From: "Greenwalt, Paul" <paul.greenwalt@intel.com>
To: Tony Nguyen <anthony.l.nguyen@intel.com>,
"Loktionov, Aleksandr" <aleksandr.loktionov@intel.com>,
Kohei Enju <kohei@enjuk.jp>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "Kitszel, Przemyslaw" <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>,
Alice Michael <alice.michael@intel.com>,
"Fijalkowski, Maciej" <maciej.fijalkowski@intel.com>,
"kohei.enju@gmail.com" <kohei.enju@gmail.com>
Subject: Re: [PATCH v1 iwl-net] ice: fix potential NULL pointer deref in error path of ice_set_ringparam()
Date: Mon, 23 Feb 2026 09:07:36 -0800 [thread overview]
Message-ID: <79b0f862-c62c-4069-b39c-2574e6025c0d@intel.com> (raw)
In-Reply-To: <81f91e12-599b-49e7-9299-cfecb994cb6f@intel.com>
On 2/20/2026 5:50 PM, Tony Nguyen wrote:
>
>
> On 2/20/2026 4:35 PM, Greenwalt, Paul wrote:
>>
>>
>> On 2/20/2026 12:04 PM, Loktionov, Aleksandr wrote:
>
> ...
>
>> Also, per Alex's comment, please target 'net'.
>
> Since this is for an Intel driver, iwl-net is the correct target.
>
> Also, as was responded, this works off changes that are only on net-
> queue at the moment.
>
> https://lore.kernel.org/intel-wired-lan/20260220204526.7514-1-
> kohei@enjuk.jp/
>
Thanks for the clarification Kohei and Tony.
Reviewed-by: Paul Greenwalt <paul.greenwalt@intel.com>
> Thanks,
> Tony
prev parent reply other threads:[~2026-02-23 17:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 18:39 [PATCH v1 iwl-net] ice: fix potential NULL pointer deref in error path of ice_set_ringparam() Kohei Enju
2026-02-20 20:04 ` Loktionov, Aleksandr
2026-02-20 20:44 ` [Intel-wired-lan] " Kohei Enju
2026-02-21 0:35 ` Greenwalt, Paul
2026-02-21 1:50 ` Tony Nguyen
2026-02-23 17:07 ` Greenwalt, Paul [this message]
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=79b0f862-c62c-4069-b39c-2574e6025c0d@intel.com \
--to=paul.greenwalt@intel.com \
--cc=aleksandr.loktionov@intel.com \
--cc=alice.michael@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kohei.enju@gmail.com \
--cc=kohei@enjuk.jp \
--cc=kuba@kernel.org \
--cc=maciej.fijalkowski@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox