From: Randy Dunlap <rdunlap@infradead.org>
To: Hemanth Selam <hemanth.selam@gmail.com>
Cc: Tony Nguyen <anthony.l.nguyen@intel.com>,
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>,
Simon Horman <horms@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH iwl-next v2 0/4] intel: fix typos in comments
Date: Mon, 7 Sep 2026 22:51:31 -0700 [thread overview]
Message-ID: <8b923faa-4676-4487-931a-98d84993517a@infradead.org> (raw)
In-Reply-To: <20260908054643.11460-1-hemanth.selam@gmail.com>
On 9/7/26 10:46 PM, Hemanth Selam wrote:
> On Mon, Sep 07, 2026 at 10:27:00AM -0700, Randy Dunlap wrote:
>> How did you choose iwl-next as the target tree?
>>
>> The closest match to that in the MAINTAINERS file is this:
>> INTEL WIRELESS WIFI LINK (iwlwifi)
> [...]
>> but the patches don't touch any of the Intel wifi drivers.
>>
>> I expect that you want net-next there, but I could just be confuzed.
>
> Sorry, the prefix is a confusing one. Here "iwl" is Intel Wired LAN, not
> iwlwifi. It is the prefix the Intel ethernet maintainers use for their
> next-queue tree, the one in MAINTAINERS under INTEL ETHERNET DRIVERS:
>
> L: intel-wired-lan@lists.osuosl.org (moderated for non-subscribers)
> T: git git://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git
>
> Intel's own developers tag patches for that tree the same way; recent
> examples on the list are the ice, idpf, ixd and libie series, all
> [PATCH iwl-next]. Since these four patches only touch
> drivers/net/ethernet/intel/ and its documentation, they go through that
> tree rather than straight to net-next.
>
> So I think iwl-next is right here, but Tony and Przemek should correct me
> if they would rather have them another way.
>
> Thanks for looking.
Thanks for the info!
--
~Randy
next prev parent reply other threads:[~2026-09-08 5:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 9:54 [PATCH iwl-next v2 0/4] intel: fix typos in comments Hemanth Selam
2026-09-07 9:54 ` [PATCH iwl-next v2 1/4] i40e: " Hemanth Selam
2026-09-11 20:59 ` Loktionov, Aleksandr
2026-09-07 9:54 ` [PATCH iwl-next v2 2/4] ice: " Hemanth Selam
2026-09-11 21:01 ` Loktionov, Aleksandr
2026-09-07 9:54 ` [PATCH iwl-next v2 3/4] ixgbevf: fix typo "enble" in comment Hemanth Selam
2026-09-11 21:02 ` Loktionov, Aleksandr
2026-09-07 9:54 ` [PATCH iwl-next v2 4/4] Documentation/eth/intel: fix repeated words in comments Hemanth Selam
2026-09-11 21:02 ` Loktionov, Aleksandr
2026-09-07 17:27 ` [PATCH iwl-next v2 0/4] intel: fix typos " Randy Dunlap
2026-09-08 5:46 ` Hemanth Selam
2026-09-08 5:51 ` Randy Dunlap [this message]
2026-09-08 6:00 ` Randy Dunlap
2026-09-09 21:07 ` Tony Nguyen
2026-09-10 0:50 ` Jakub Kicinski
2026-09-10 1:00 ` patchwork-bot+netdevbpf
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=8b923faa-4676-4487-931a-98d84993517a@infradead.org \
--to=rdunlap@infradead.org \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hemanth.selam@gmail.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=skhan@linuxfoundation.org \
/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