From: Thomas Monjalon <thomas@monjalon.net>
To: Aaron Conole <aconole@redhat.com>, Ferruh Yigit <ferruh.yigit@intel.com>
Cc: John Daley <johndale@cisco.com>,
arybchenko@solarflare.com, dev@dpdk.org,
Hyong Youb Kim <hyonkim@cisco.com>,
Ali Alnubani <alialnu@nvidia.com>, "ci@dpdk.org" <ci@dpdk.org>,
David Marchand <david.marchand@redhat.com>
Subject: Re: [PATCH 1/3] net/enic: add support for eCPRI matching
Date: Thu, 27 Jan 2022 09:07:21 +0100 [thread overview]
Message-ID: <8056915.NyiUUSuA9g@thomas> (raw)
In-Reply-To: <a398fffe-65cf-e360-afe9-4caa649dcfa1@intel.com>
26/01/2022 15:01, Ferruh Yigit:
> On 1/26/2022 2:00 PM, Ferruh Yigit wrote:
> > On 1/14/2022 3:10 AM, John Daley wrote:
> >> eCPRI message can be over Ethernet layer (.1Q supported also) or over
> >> UDP layer. Message header formats are the same in these two variants.
> >>
> >> Only up though the first packet header in the PDU can be matched.
> >> RSS on the eCPRI header fields is not supported.
> >>
> >> Signed-off-by: John Daley<johndale@cisco.com>
> >> Reviewed-by: Hyong Youb Kim<hyonkim@cisco.com>
> >> ---
> >> doc/guides/rel_notes/release_22_03.rst | 1 +
> >> drivers/net/enic/enic_fm_flow.c | 65 ++++++++++++++++++++++++++
> >> 2 files changed, 66 insertions(+)
> >
> > Documentation update is missing, can you please fix?
> >
> > $ ./devtools/check-doc-vs-code.sh
> > rte_flow doc out of sync for enic
> > item ecpri
>
> Hi Thomas,
>
> Can we add './devtools/check-doc-vs-code.sh' check to CI, what do you think?
Yes of course
next prev parent reply other threads:[~2022-01-27 8:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 3:10 [PATCH 0/3] enic PMD patches John Daley
2022-01-14 3:10 ` [PATCH 1/3] net/enic: add support for eCPRI matching John Daley
2022-01-26 14:00 ` Ferruh Yigit
2022-01-26 14:01 ` Ferruh Yigit
2022-01-27 8:07 ` Thomas Monjalon [this message]
2022-01-26 21:48 ` [PATCH v2] " John Daley
2022-01-27 12:15 ` Ferruh Yigit
2022-01-27 18:55 ` [PATCH v3] " John Daley
2022-01-14 3:10 ` [PATCH 2/3] net/enic: update VIC firmware API John Daley
2022-01-14 3:10 ` [PATCH 3/3] net/enic: support max descriptors allowed by adapter John Daley
2022-01-26 14:01 ` Ferruh Yigit
2022-01-26 21:55 ` [PATCH v2] " John Daley
2022-01-27 19:10 ` [PATCH v3] " John Daley
2022-01-28 12:58 ` Ferruh Yigit
2022-01-28 17:58 ` [PATCH v4 1/3] net/enic: add support for eCPRI matching John Daley
2022-01-28 17:58 ` [PATCH v4 2/3] net/enic: update VIC firmware API John Daley
2022-01-28 17:58 ` [PATCH v4 3/3] net/enic: support max descriptors allowed by adapter John Daley
2022-01-31 11:46 ` [PATCH v4 1/3] net/enic: add support for eCPRI matching Ferruh Yigit
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=8056915.NyiUUSuA9g@thomas \
--to=thomas@monjalon.net \
--cc=aconole@redhat.com \
--cc=alialnu@nvidia.com \
--cc=arybchenko@solarflare.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hyonkim@cisco.com \
--cc=johndale@cisco.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).