public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Joe Damato <jdamato@fastly.com>, <florian@bezdeka.de>,
	<netdev@vger.kernel.org>, <vitaly.lifshits@intel.com>,
	<avigailx.dahan@intel.com>, <stable@vger.kernel.org>,
	Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	"Jesper Dangaard Brouer" <hawk@kernel.org>,
	John Fastabend <john.fastabend@gmail.com>,
	"Przemek Kitszel" <przemyslaw.kitszel@intel.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, <bpf@vger.kernel.org>,
	<intel-wired-lan@lists.osuosl.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH iwl-net] igc: Fix XSK queue NAPI ID mapping
Date: Fri, 7 Mar 2025 13:37:35 -0800	[thread overview]
Message-ID: <8d3bafbc-eb45-49c5-be78-cec96be52f82@intel.com> (raw)
In-Reply-To: <9ddf6293-6cb0-47ea-a0e7-cad7d33c2535@intel.com>



On 3/6/2025 10:31 AM, Tony Nguyen wrote:
> On 3/6/2025 8:45 AM, Joe Damato wrote:
>> On Thu, Mar 06, 2025 at 05:27:38PM +0100, florian@bezdeka.de wrote:
> 
> ...
> 
>>> Btw: I got this patch via stable. It doesn't make sense to send it
>>> to stable where this patch does not apply.
>>
>> Maybe I made a mistake, but as far as I can tell the commit under
>> fixes is in 6.14-rc*:
>>
>> $ git tag --contains b65969856d4f
>> v6.14-rc1
>> v6.14-rc2
>> v6.14-rc3
>> v6.14-rc4
>>
>> So, I think this change is:
>>    - Correct
>>    - Definitely a "fixes" and should go to iwl-net
>>    - But maybe does not need to CC stable ?
>>
>> If the Intel folks would like me to resend with some change please
>> let me know.
> 
> Seems like the only change needed is the omission of stable. If so, no 
> changes need. I can take care of that when sending on to netdev.

I missed this comment [1] when I responded; I can make this change though.

Thanks,
Tony

[1] 
https://lore.kernel.org/intel-wired-lan/9ddf6293-6cb0-47ea-a0e7-cad7d33c2535@intel.com/T/#m47dd425fb4de4c1738839c2f8253ec51718d299e


  reply	other threads:[~2025-03-07 21:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-05 18:09 [PATCH iwl-net] igc: Fix XSK queue NAPI ID mapping Joe Damato
2025-03-05 19:15 ` Gerhard Engleder
2025-03-06 16:27 ` florian
2025-03-06 16:45   ` Joe Damato
2025-03-06 18:31     ` Tony Nguyen
2025-03-07 21:37       ` Tony Nguyen [this message]
2025-03-25 16:23 ` [Intel-wired-lan] " Mor Bar-Gabay

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=8d3bafbc-eb45-49c5-be78-cec96be52f82@intel.com \
    --to=anthony.l.nguyen@intel.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=ast@kernel.org \
    --cc=avigailx.dahan@intel.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=florian@bezdeka.de \
    --cc=hawk@kernel.org \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jdamato@fastly.com \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=vitaly.lifshits@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox