From: Jerin Jacob <jerinjacobk@gmail.com>
To: "Naga Harish K, S V" <s.v.naga.harish.k@intel.com>
Cc: Rahul Bhansali <rbhansali@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>, Jerin Jacob <jerinj@marvell.com>,
"Kundapura, Ganapati" <ganapati.kundapura@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [PATCH v3] eventdev/eth_rx: fix timestamp field register in mbuf
Date: Wed, 27 Sep 2023 10:28:53 +0530 [thread overview]
Message-ID: <CALBAE1Op+9JT53kqM=MKK79-p=09xoviKAZ+39N6akrbJ8y0ew@mail.gmail.com> (raw)
In-Reply-To: <DM6PR11MB38683507B1CDC72D45A6F017A1C3A@DM6PR11MB3868.namprd11.prod.outlook.com>
On Wed, Sep 27, 2023 at 2:41 AM Naga Harish K, S V
<s.v.naga.harish.k@intel.com> wrote:
>
>
>
> > -----Original Message-----
> > From: Rahul Bhansali <rbhansali@marvell.com>
> > Sent: Wednesday, September 20, 2023 10:18 PM
> > To: dev@dpdk.org; Naga Harish K, S V <s.v.naga.harish.k@intel.com>; Jerin
> > Jacob <jerinj@marvell.com>; Kundapura, Ganapati
> > <ganapati.kundapura@intel.com>
> > Cc: Rahul Bhansali <rbhansali@marvell.com>; stable@dpdk.org
> > Subject: [PATCH v3] eventdev/eth_rx: fix timestamp field register in mbuf
> >
> > For eventdev internal port, timestamp dynamic field registration in mbuf is not
> > required as that will be done from net device.
> > For SW eventdev, Rx timestamp field registration will be done during Rxa
> > service initialization.
> >
> > Fixes: 83ab470d1259 ("eventdev/eth_rx: use timestamp as dynamic mbuf
> > field")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Rahul Bhansali <rbhansali@marvell.com>
>
> Acked-by: Naga Harish K S V <s.v.naga.harish.k@intel.com>
Applied to dpdk-next-net-eventdev/for-main. Thanks
prev parent reply other threads:[~2023-09-27 4:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 8:25 [PATCH] " Rahul Bhansali
2023-09-19 16:29 ` Jerin Jacob
2023-09-25 10:18 ` Naga Harish K, S V
2023-09-26 7:37 ` Jerin Jacob
2023-09-20 12:32 ` Naga Harish K, S V
2023-09-20 16:17 ` Rahul Bhansali
2023-09-20 16:32 ` [PATCH v2] " Rahul Bhansali
2023-09-20 16:48 ` [PATCH v3] " Rahul Bhansali
2023-09-26 7:04 ` Naga Harish K, S V
2023-09-27 4:58 ` Jerin Jacob [this message]
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='CALBAE1Op+9JT53kqM=MKK79-p=09xoviKAZ+39N6akrbJ8y0ew@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=ganapati.kundapura@intel.com \
--cc=jerinj@marvell.com \
--cc=rbhansali@marvell.com \
--cc=s.v.naga.harish.k@intel.com \
--cc=stable@dpdk.org \
/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).