From: Kohei Enju <kohei@enjuk.jp>
To: jacob.e.keller@intel.com
Cc: aleksander.lobakin@intel.com, aleksandr.loktionov@intel.com,
andrew+netdev@lunn.ch, anthony.l.nguyen@intel.com,
davem@davemloft.net, edumazet@google.com,
intel-wired-lan@lists.osuosl.org, kohei.enju@gmail.com,
kohei@enjuk.jp, kuba@kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, przemyslaw.kitszel@intel.com
Subject: Re: [PATCH v1 iwl-next] ice: fix NULL pointer dereference when
Date: Tue, 3 Feb 2026 03:23:35 +0000 [thread overview]
Message-ID: <20260203032350.3221-1-kohei@enjuk.jp> (raw)
In-Reply-To: <bcefc3ee-4704-483a-8271-01677e47eb8b@intel.com>
On Mon, 2 Feb 2026 16:31:39 -0800, Jacob Keller wrote:
> > I see the Fixes: commit exists in only tnguy/next-queue.git, so I'm
> > sending this patch to iwl-next, not iwl-net.
> >
> > Also IIUC dev-queue in tnguy/next-queue.git is rebased continuously, so
> > the commit hash will be stale soon, and I don't know how to handle this.
> >
>
> Yea. Including the full subject line should be sufficient for Tony to
> find this.
I see :)
>
> > I'd appreciate it if iwl-folks know the way to handle it. Thanks!
>
> Ideally we can squash this in with the implementation patches and
> include your Co-developed-by and Signed-off-by tags if you would agree
> to that?
That sounds good, and I agree to do so.
If I need to take some actions, please let me know.
next prev parent reply other threads:[~2026-02-03 3:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 16:17 [PATCH v1 iwl-next] ice: fix NULL pointer dereference when changing RX queue length Kohei Enju
2026-02-02 16:28 ` Loktionov, Aleksandr
2026-02-03 0:31 ` Jacob Keller
2026-02-03 3:23 ` Kohei Enju [this message]
2026-02-04 11:52 ` Alexander Lobakin
2026-02-04 13:06 ` [PATCH v1 iwl-next] ice: fix NULL pointer dereference when 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=20260203032350.3221-1-kohei@enjuk.jp \
--to=kohei@enjuk.jp \
--cc=aleksander.lobakin@intel.com \
--cc=aleksandr.loktionov@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=jacob.e.keller@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox