From: Kohei Enju <kohei@enjuk.jp>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
Simon Horman <horms@kernel.org>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
dima.ruinskiy@intel.com, kohei.enju@gmail.com
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v2 0/2] igc: enable build_skb path
Date: Fri, 20 Mar 2026 15:05:23 +0900 [thread overview]
Message-ID: <abzhZsk5FdB2eWeN@x1> (raw)
In-Reply-To: <20260319161140.GI1753385@horms.kernel.org>
On 03/19 16:11, Simon Horman wrote:
> On Tue, Mar 17, 2026 at 06:21:44AM +0000, Kohei Enju wrote:
> > This series enables the build_skb RX path in igc, which is currently not
> > enabled in any configuration.
> >
> > Patch 1/2 adds missing RX hardware timestamp handling in the build_skb
> > path.
> > Patch 2/2 enables the build_skb path when XDP is inactive and other
> > conditions are met.
> >
> > Tested on Intel Corporation Ethernet Controller I226-V (rev 04).
> >
> > Changes:
> > v2:
> > - don't insist on reverse christmas tree, reducing net diff in the
> > patch 1/2 (Dima)
> > v1: https://lore.kernel.org/intel-wired-lan/20260307182808.155027-1-kohei@enjuk.jp/
> >
> > Kohei Enju (2):
> > igc: set RX hardware timestamps in igc_build_skb()
> > igc: enable build_skb on the non-XDP small-frame RX path
>
> For the series:
>
> Reviewed-by: Simon Horman <horms@kernel.org>
Hi Tony, thanks for applying this series to next-queue.
I have a question about the process of patch submission.
Sometimes reviewers give RB tags for a whole series like this, but I
think that those tags on the cover letter are not collected
automatically, right?
In this case, should I add RB tags to each patch if I respin for other
reasons, or what is the recommended way to handle this?
WARNING: multiple messages have this Message-ID (diff)
From: Kohei Enju <kohei@enjuk.jp>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
Simon Horman <horms@kernel.org>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
dima.ruinskiy@intel.com, kohei.enju@gmail.com
Subject: Re: [PATCH iwl-next v2 0/2] igc: enable build_skb path
Date: Fri, 20 Mar 2026 15:05:23 +0900 [thread overview]
Message-ID: <abzhZsk5FdB2eWeN@x1> (raw)
In-Reply-To: <20260319161140.GI1753385@horms.kernel.org>
On 03/19 16:11, Simon Horman wrote:
> On Tue, Mar 17, 2026 at 06:21:44AM +0000, Kohei Enju wrote:
> > This series enables the build_skb RX path in igc, which is currently not
> > enabled in any configuration.
> >
> > Patch 1/2 adds missing RX hardware timestamp handling in the build_skb
> > path.
> > Patch 2/2 enables the build_skb path when XDP is inactive and other
> > conditions are met.
> >
> > Tested on Intel Corporation Ethernet Controller I226-V (rev 04).
> >
> > Changes:
> > v2:
> > - don't insist on reverse christmas tree, reducing net diff in the
> > patch 1/2 (Dima)
> > v1: https://lore.kernel.org/intel-wired-lan/20260307182808.155027-1-kohei@enjuk.jp/
> >
> > Kohei Enju (2):
> > igc: set RX hardware timestamps in igc_build_skb()
> > igc: enable build_skb on the non-XDP small-frame RX path
>
> For the series:
>
> Reviewed-by: Simon Horman <horms@kernel.org>
Hi Tony, thanks for applying this series to next-queue.
I have a question about the process of patch submission.
Sometimes reviewers give RB tags for a whole series like this, but I
think that those tags on the cover letter are not collected
automatically, right?
In this case, should I add RB tags to each patch if I respin for other
reasons, or what is the recommended way to handle this?
next prev parent reply other threads:[~2026-03-20 6:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 6:21 [Intel-wired-lan] [PATCH iwl-next v2 0/2] igc: enable build_skb path Kohei Enju
2026-03-17 6:21 ` Kohei Enju
2026-03-17 6:21 ` [Intel-wired-lan] [PATCH iwl-next v2 1/2] igc: set RX hardware timestamps in igc_build_skb() Kohei Enju
2026-03-17 6:21 ` Kohei Enju
2026-03-18 15:56 ` [Intel-wired-lan] " Ruinskiy, Dima
2026-03-18 15:56 ` Ruinskiy, Dima
2026-03-23 17:21 ` [Intel-wired-lan] " Dahan, AvigailX
2026-03-17 6:21 ` [Intel-wired-lan] [PATCH iwl-next v2 2/2] igc: enable build_skb on the non-XDP small-frame RX path Kohei Enju
2026-03-17 6:21 ` Kohei Enju
2026-03-18 15:57 ` [Intel-wired-lan] " Ruinskiy, Dima
2026-03-18 15:57 ` Ruinskiy, Dima
2026-03-23 17:23 ` [Intel-wired-lan] " Dahan, AvigailX
2026-03-19 16:11 ` [Intel-wired-lan] [PATCH iwl-next v2 0/2] igc: enable build_skb path Simon Horman
2026-03-19 16:11 ` Simon Horman
2026-03-20 6:05 ` Kohei Enju [this message]
2026-03-20 6:05 ` Kohei Enju
2026-03-20 20:30 ` [Intel-wired-lan] " Tony Nguyen
2026-03-20 20:30 ` Tony Nguyen
2026-03-21 7:13 ` [Intel-wired-lan] " Kohei Enju
2026-04-19 4:54 ` Kohei Enju
2026-04-19 4:54 ` Kohei Enju
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=abzhZsk5FdB2eWeN@x1 \
--to=kohei@enjuk.jp \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=dima.ruinskiy@intel.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kohei.enju@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.