From: "Naga Harish K, S V" <s.v.naga.harish.k@intel.com>
To: Jerin Jacob <jerinjacobk@gmail.com>,
Rahul Bhansali <rbhansali@marvell.com>
Cc: "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] eventdev/eth_rx: fix timestamp field register in mbuf
Date: Mon, 25 Sep 2023 10:18:05 +0000 [thread overview]
Message-ID: <DM6PR11MB3868F3DE01C6627615863DD1A1FCA@DM6PR11MB3868.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CALBAE1OgA-e8Me9NwX1MNO0AceWXUDsvf7opZo1MKD=M06t50g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]
As per the DPDK contribution guidelines,
Ideally, the review should be done within 1 week of patch submission to the mailing list.
https://doc.dpdk.org/guides/contributing/patches.html
Surprised to see this review request ping message the very next day of the patch.
Better to follow the contribution guidelines.
-Harish
________________________________
From: Jerin Jacob <jerinjacobk@gmail.com>
Sent: Tuesday, September 19, 2023 9:59 PM
To: Rahul Bhansali <rbhansali@marvell.com>
Cc: dev@dpdk.org <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>; stable@dpdk.org <stable@dpdk.org>
Subject: Re: [PATCH] eventdev/eth_rx: fix timestamp field register in mbuf
On Mon, Sep 18, 2023 at 6:46 PM Rahul Bhansali <rbhansali@marvell.com> wrote:
>
> 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 Rx queue add operation as per device capabilities and
> offload configuration.
>
> Fixes: 83ab470d1259 ("eventdev/eth_rx: use timestamp as dynamic mbuf field")
> Cc: stable@dpdk.org
>
> Signed-off-by: Rahul Bhansali <rbhansali@marvell.com>
Ping for review from maintainer.
[-- Attachment #2: Type: text/html, Size: 4735 bytes --]
next prev parent reply other threads:[~2023-09-25 10:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 8:25 Rahul Bhansali
2023-09-19 16:29 ` Jerin Jacob
2023-09-25 10:18 ` Naga Harish K, S V [this message]
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
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=DM6PR11MB3868F3DE01C6627615863DD1A1FCA@DM6PR11MB3868.namprd11.prod.outlook.com \
--to=s.v.naga.harish.k@intel.com \
--cc=dev@dpdk.org \
--cc=ganapati.kundapura@intel.com \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=rbhansali@marvell.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).