From: Jakub Kicinski <kuba@kernel.org>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: Jacob Keller <jacob.e.keller@intel.com>,
Petr Oros <poros@redhat.com>,
Maciej Fijalkowski <maciej.fijalkowski@intel.com>,
Magnus Karlsson <magnus.karlsson@gmail.com>,
<netdev@vger.kernel.org>, Paolo Abeni <pabeni@redhat.com>,
<edumazet@kernel.org>, <davem@davemloft.net>,
<andrew+netdev@lunn.ch>, <horms@kernel.org>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Marcin Szycik <marcin.szycik@linux.intel.com>,
Aleksandr Loktionov <aleksandr.loktionov@intel.com>,
<intel-wired-lan@lists.osuosl.org>
Subject: Re: [PATCH net 0/6][pull request] Intel Wired LAN Driver Updates 2026-11-13 (ice)
Date: Sat, 21 Nov 2026 16:28:59 -0800 [thread overview]
Message-ID: <20261121162859.3522ab89@kernel.org> (raw)
In-Reply-To: <fe1ce4cf-3400-4a87-8e46-072563f8fe9d@intel.com>
On Thu, 19 Nov 2026 10:07:10 -0800 Tony Nguyen wrote:
> An idea, but this would still increase the queue for netdev, would be a
> separate budget for non-Intel authored patches. This would allow
> community patches to continue flowing without being blocked by Intel work.
No extra patch budget will be provided.
As I think I mentioned multiple times netdev maintainers are happy to
take patches directly. My understanding is that it's Intel that wants
to feed the patches thru their internal QA and have the ability to work
on timelines, let's just say, different than netdev works on.
We wait for an ack/review of a maintainer, from Intel such acks never
come. Przemek / Tony can start acking things directly on netdev.
You can also add another maintainer to your entry, or split it up
and designate even more people.
IOW I agree that the Intel process feels dated, and life would be
easier if Intel switched to an upstream first process.
next prev parent reply other threads:[~2026-11-22 0:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 23:12 [PATCH net 0/6][pull request] Intel Wired LAN Driver Updates 2026-11-13 (ice) Tony Nguyen
2026-11-13 23:12 ` [PATCH net 1/6] ice: use global queue index in TC to-queue offload Tony Nguyen
2026-11-17 23:54 ` netdev-bot+sashiko
2026-11-13 23:12 ` [PATCH net 2/6] ice: skip per-VLAN promisc rules when default VSI Rx rule is set Tony Nguyen
2026-11-17 23:54 ` netdev-bot+sashiko
2026-11-19 8:23 ` Petr Oros
2026-11-13 23:12 ` [PATCH net 3/6] ice: preserve uplink DFLT Rx rule on switchdev release Tony Nguyen
2026-11-17 23:54 ` netdev-bot+sashiko
2026-11-19 8:36 ` Petr Oros
2026-11-13 23:12 ` [PATCH net 4/6] ice: Fix incorrect LLDP filter assumptions Tony Nguyen
2026-11-17 23:54 ` netdev-bot+sashiko
2026-11-13 23:12 ` [PATCH net 5/6] ice: propagate ETH56G deskew poll failures Tony Nguyen
2026-11-17 23:54 ` netdev-bot+sashiko
2026-11-13 23:12 ` [PATCH net 6/6] ice: allow reading the last byte of the NVM and Shadow RAM regions Tony Nguyen
2026-11-13 23:18 ` [PATCH net 0/6][pull request] Intel Wired LAN Driver Updates 2026-11-13 (ice) netdev-bot+sinfo
2026-11-18 11:59 ` Petr Oros
2026-11-18 13:37 ` Magnus Karlsson
2026-11-18 13:48 ` Maciej Fijalkowski
2026-11-18 13:51 ` Petr Oros
2026-11-18 23:00 ` Jacob Keller
2026-11-19 18:07 ` Tony Nguyen
2026-11-22 0:28 ` Jakub Kicinski [this message]
2026-11-22 0:40 ` 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=20261121162859.3522ab89@kernel.org \
--to=kuba@kernel.org \
--cc=aleksandr.loktionov@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@gmail.com \
--cc=marcin.szycik@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=poros@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