[PATCH] eventdev/eth_rx: fix timestamp field register in mbuf

[Jerin Jacob]

On Mon, Sep 25, 2023 at 3:48 PM Naga Harish K, S V
<s.v.naga.harish.k at 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 at 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