DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ivan Malov <Ivan.Malov@oktetlabs.ru>
To: Ferruh Yigit <ferruh.yigit@intel.com>, dev@dpdk.org
Cc: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: Re: [dpdk-dev] [PATCH 1/3] common/sfc_efx/base: update MCDI headers
Date: Fri, 30 Apr 2021 20:05:42 +0300	[thread overview]
Message-ID: <cc71bcc0-e708-1cc3-670c-b970b49d9efa@oktetlabs.ru> (raw)
In-Reply-To: <b20d2a2e-e2b6-d077-173a-63b92ec326ae@intel.com>

Hi Ferruh,

These changes are imported. Furthermore, originally, these files are 
auto-generated, so in order to fix spelling I can't just apply my edits 
to the imported changes. The fixes are to be made in the original 
source, and I believe this should be somehow discussed internally.

So, the changeset is either to be applied "as it is" (meaning that the 
fixes are expected to be submitted with future updates) or postponed. 
Maybe Andrew can advise.

Yes, I see the spelling warnings, they're pretty much valid. But some of 
them are.. questionable. In particular, "misspelling" of the word HIST 
in MC_CMD_LTSSM_HIST_MSGSET. For sure, the suggested replacement doesn't 
quite fit the intended meaning of the macro.

Thank you.

On 30/04/2021 18:56, Ferruh Yigit wrote:
> On 4/28/2021 10:49 AM, Ivan Malov wrote:
>> From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
>>
>> Signed-off-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
>> Signed-off-by: Ivan Malov <ivan.malov@oktetlabs.ru>
>> ---
>>   drivers/common/sfc_efx/base/efx_regs_mcdi.h   | 3509 +++++++++++++++--
>>   .../common/sfc_efx/base/efx_regs_mcdi_aoe.h   |  142 +-
>>   .../common/sfc_efx/base/efx_regs_mcdi_strs.h  |    2 +-
>>   3 files changed, 3312 insertions(+), 341 deletions(-)
> 
> Hi Ivan,
> 
> There are some checkpatch spelling warnings, can you please check them?
> 
> Also is there a versioning on the MCDI, if so you may want to document the
> updated version in driver guide and/or release notes.
> 

-- 
Ivan M

  reply	other threads:[~2021-04-30 17:05 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28  9:49 Ivan Malov
2021-04-28  9:49 ` [dpdk-dev] [PATCH 2/3] common/sfc_efx/base: add MAE VLAN presence match bits Ivan Malov
2021-04-28 10:08   ` Kinsella, Ray
2021-04-28 11:09     ` Ivan Malov
2021-04-30 14:49   ` Kinsella, Ray
2021-04-28  9:49 ` [dpdk-dev] [PATCH 3/3] net/sfc: support matching on VLAN presence in transfer rules Ivan Malov
2021-04-30 15:56 ` [dpdk-dev] [PATCH 1/3] common/sfc_efx/base: update MCDI headers Ferruh Yigit
2021-04-30 17:05   ` Ivan Malov [this message]
2021-05-04  7:50     ` Ferruh Yigit
2021-05-04  8:15       ` Andrew Rybchenko
2021-05-22 19:32 ` [dpdk-dev] [PATCH v2 0/3] Match On VLAN Presence In Transfer Flows Ivan Malov
2021-05-22 19:32 ` [dpdk-dev] [PATCH v2 1/3] common/sfc_efx/base: update MCDI headers Ivan Malov
2021-05-22 19:32 ` [dpdk-dev] [PATCH v2 2/3] common/sfc_efx/base: add MAE VLAN presence match bits Ivan Malov
2021-05-22 19:32 ` [dpdk-dev] [PATCH v2 3/3] net/sfc: support matching on VLAN presence in transfer rules Ivan Malov
2021-05-24 11:18 ` [dpdk-dev] [PATCH v3 0/3] Match On VLAN Presence In Transfer Flows Ivan Malov
2021-05-24 11:18 ` [dpdk-dev] [PATCH v3 1/3] common/sfc_efx/base: update MCDI headers Ivan Malov
2021-05-24 11:18 ` [dpdk-dev] [PATCH v3 2/3] common/sfc_efx/base: add MAE VLAN presence match bits Ivan Malov
2021-05-24 11:18 ` [dpdk-dev] [PATCH v3 3/3] net/sfc: support matching on VLAN presence in transfer rules Ivan Malov
2021-05-24 11:48 ` [dpdk-dev] [PATCH v4 0/3] Match On VLAN Presence In Transfer Flows Ivan Malov
2021-05-24 11:48   ` [dpdk-dev] [PATCH v4 1/3] common/sfc_efx/base: update MCDI headers Ivan Malov
2021-05-24 11:48   ` [dpdk-dev] [PATCH v4 2/3] common/sfc_efx/base: add MAE VLAN presence match bits Ivan Malov
2021-05-24 11:48   ` [dpdk-dev] [PATCH v4 3/3] net/sfc: support matching on VLAN presence in transfer rules Ivan Malov
2021-07-07 10:00   ` [dpdk-dev] [PATCH v4 0/3] Match On VLAN Presence In Transfer Flows David Marchand

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cc71bcc0-e708-1cc3-670c-b970b49d9efa@oktetlabs.ru \
    --to=ivan.malov@oktetlabs.ru \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).