From: Jerin Jacob <jerinjacobk@gmail.com>
To: "Naga Harish K, S V" <s.v.naga.harish.k@intel.com>,
Qi Zhang <qi.z.zhang@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Ali Alnubani <alialnu@nvidia.com>,
Ferruh Yigit <ferruh.yigit@amd.com>,
David Marchand <david.marchand@redhat.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
Raslan Darawsheh <rasland@nvidia.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
cheng1.jiang@intel.com, Akhil Goyal <gakhil@marvell.com>,
"Richardson, Bruce" <bruce.richardson@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] eventdev/eth_rx: fix timestamp field register in mbuf
Date: Tue, 26 Sep 2023 13:07:30 +0530 [thread overview]
Message-ID: <CALBAE1PgU7p=kpx=7hKo5SsPYxmakCTayh=YMoWr4JV4J4vnjw@mail.gmail.com> (raw)
In-Reply-To: <DM6PR11MB3868F3DE01C6627615863DD1A1FCA@DM6PR11MB3868.namprd11.prod.outlook.com>
On Mon, Sep 25, 2023 at 3:48 PM Naga Harish K, S V
<s.v.naga.harish.k@intel.com> wrote:
>
> 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.
+ @Thomas Monjalon @Ali Alnubani @Ferruh Yigit @David Marchand
@Andrew Rybchenko @Ajit Khaparde @Qi Zhang @Raslan Darawsheh @Maxime
Coquelin @cheng1.jiang@intel.com @Akhil Goyal @Richardson, Bruce
Yes, and I agree, and thanks for reporting this. I usually merge a set
of patches together and call for review action if something pending in
my list. I was not looking to the timestamp as it was manual.
Seems like good feature additions in patchwork if it not ready
available or if available then we can configure for DPDK.
i.e., if patchwork can track email time for the patch and flag for no
reviewed happened in N days(N as configurable) to help maintainers.
Also, Get list of pending patches on component maintainers(I think,
currently we can get only based on tree delegation) not per component
maintainer.
>
> -Harish
next prev parent reply other threads:[~2023-09-26 7:37 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
2023-09-26 7:37 ` Jerin Jacob [this message]
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='CALBAE1PgU7p=kpx=7hKo5SsPYxmakCTayh=YMoWr4JV4J4vnjw@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=ajit.khaparde@broadcom.com \
--cc=alialnu@nvidia.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=bruce.richardson@intel.com \
--cc=cheng1.jiang@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=gakhil@marvell.com \
--cc=ganapati.kundapura@intel.com \
--cc=jerinj@marvell.com \
--cc=maxime.coquelin@redhat.com \
--cc=qi.z.zhang@intel.com \
--cc=rasland@nvidia.com \
--cc=rbhansali@marvell.com \
--cc=s.v.naga.harish.k@intel.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).