Linux Documentation
 help / color / mirror / Atom feed
From: Jacob Keller <jacob.e.keller@intel.com>
To: Alexander Lobakin <aleksander.lobakin@intel.com>,
	Aleksandr Loktionov <aleksandr.loktionov@intel.com>
Cc: Larysa Zaremba <larysa.zaremba@intel.com>,
	Tony Nguyen <anthony.l.nguyen@intel.com>, <davem@davemloft.net>,
	<pabeni@redhat.com>, <edumazet@google.com>,
	<andrew+netdev@lunn.ch>, <netdev@vger.kernel.org>,
	<przemyslaw.kitszel@intel.com>, <sridhar.samudrala@intel.com>,
	<anjali.singhai@intel.com>, <michal.swiatkowski@linux.intel.com>,
	<maciej.fijalkowski@intel.com>, <emil.s.tantilov@intel.com>,
	<madhu.chittim@intel.com>, <joshua.a.hay@intel.com>,
	<jayaprakash.shanmugam@intel.com>, <jiri@resnulli.us>,
	<horms@kernel.org>, <corbet@lwn.net>, <richardcochran@gmail.com>,
	<linux-doc@vger.kernel.org>, <tatyana.e.nikolova@intel.com>,
	<krzysztof.czurylo@intel.com>, <jgg@ziepe.ca>, <leon@kernel.org>,
	<linux-rdma@vger.kernel.org>,
	Samuel Salin <Samuel.salin@intel.com>,
	NXNE CNSE OSDT ITP Upstreaming
	<nxne.cnse.osdt.itp.upstreaming@intel.com>,
	Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH net-next v3 01/14] virtchnl: create 'include/linux/intel' and move necessary header files
Date: Tue, 26 May 2026 14:36:59 -0700	[thread overview]
Message-ID: <079fdc7a-086d-4f99-a97a-b95cb19af322@intel.com> (raw)
In-Reply-To: <d3191a29-0ce8-4338-80b8-a49c53c1a472@intel.com>

On 5/26/2026 7:45 AM, Alexander Lobakin wrote:
> Re review score -- I noticed that as well and have been focusing on
> reviews more than sending patches, *but*:
> 
> To Aleksandr:
> 
> Please *stop* spamming IWL/netdev with patches. This doesn't help at all.
> Or at least do minimum 1 review per each patch you send.
> 

+1. I was actually thinking about some sort of limit on outstanding
patches/series in the Intel Wired LAN patchwork. I was noticing that we
have a lot of minor cleanups sitting in IWL queue for months while I was
covering for Tony.

> The imbalance you (not only, but mostly) create will only lead to that
> we won't be able to send anything at all.
> 
> To you and sorta everyone from Intel:
> 
> Please focus more on reviews and wait with sending stuff until Intel is
> back to the top 10 reviewers and has at least +/- neutral score.
> 

I know I've been a bit lacking in review last few months, with a lot on
my plate. I'm hoping to improve over the next release.

> Most of stuff coming from Intel right now is not critical for customers
> and users, by doing that you paralyze really important series.
> 
> Thanks,
> Olek


  reply	other threads:[~2026-05-26 21:37 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15 22:44 [PATCH net-next v3 00/14][pull request] Introduce iXD driver Tony Nguyen
2026-05-15 22:44 ` [PATCH net-next v3 01/14] virtchnl: create 'include/linux/intel' and move necessary header files Tony Nguyen
2026-05-21  0:52   ` Jakub Kicinski
2026-05-21  9:28     ` Larysa Zaremba
2026-05-21 13:56       ` Jakub Kicinski
2026-05-22 11:08         ` Alexander Lobakin
2026-05-22 15:40           ` Jakub Kicinski
2026-05-26 14:45             ` Alexander Lobakin
2026-05-26 21:36               ` Jacob Keller [this message]
2026-05-15 22:44 ` [PATCH net-next v3 02/14] libie: add PCI device initialization helpers to libie Tony Nguyen
2026-05-18  6:46   ` Larysa Zaremba
2026-05-18 21:54   ` Bjorn Helgaas
2026-05-19  8:20     ` Philipp Stanner
2026-05-19 10:03       ` Larysa Zaremba
2026-05-15 22:44 ` [PATCH net-next v3 03/14] libeth: allow to create fill queues without NAPI Tony Nguyen
2026-05-21  1:49   ` Jakub Kicinski
2026-05-21 10:07     ` Larysa Zaremba
2026-05-15 22:44 ` [PATCH net-next v3 04/14] libie: add control queue support Tony Nguyen
2026-05-18  7:02   ` Larysa Zaremba
2026-05-15 22:44 ` [PATCH net-next v3 05/14] libie: add bookkeeping support for control queue messages Tony Nguyen
2026-05-18  7:24   ` Larysa Zaremba
2026-05-21  1:51   ` Jakub Kicinski
2026-05-21  8:25     ` Larysa Zaremba
2026-05-15 22:44 ` [PATCH net-next v3 06/14] idpf: remove 'vport_params_reqd' field Tony Nguyen
2026-05-15 22:44 ` [PATCH net-next v3 07/14] idpf: refactor idpf to use libie_pci APIs Tony Nguyen
2026-05-18  7:40   ` Larysa Zaremba
2026-05-15 22:44 ` [PATCH net-next v3 08/14] idpf: refactor idpf to use libie control queues Tony Nguyen
2026-05-18  8:01   ` Larysa Zaremba
2026-05-18 10:14     ` Larysa Zaremba
2026-05-15 22:44 ` [PATCH net-next v3 09/14] idpf: make mbx_task queueing and cancelling more consistent Tony Nguyen
2026-05-15 22:44 ` [PATCH net-next v3 10/14] idpf: print a debug message and bail in case of non-event ctlq message Tony Nguyen
2026-05-15 22:44 ` [PATCH net-next v3 11/14] ixd: add basic driver framework for Intel(R) Control Plane Function Tony Nguyen
2026-05-18  8:32   ` Larysa Zaremba
2026-05-15 22:44 ` [PATCH net-next v3 12/14] ixd: add reset checks and initialize the mailbox Tony Nguyen
2026-05-18  9:12   ` Larysa Zaremba
2026-05-15 22:44 ` [PATCH net-next v3 13/14] ixd: add the core initialization Tony Nguyen
2026-05-18 10:01   ` Larysa Zaremba
2026-05-18 10:10   ` Larysa Zaremba
2026-05-15 22:44 ` [PATCH net-next v3 14/14] ixd: add devlink support Tony Nguyen
2026-05-18 10:11   ` Larysa Zaremba
2026-05-18 10:23 ` [PATCH net-next v3 00/14][pull request] Introduce iXD driver Larysa Zaremba

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=079fdc7a-086d-4f99-a97a-b95cb19af322@intel.com \
    --to=jacob.e.keller@intel.com \
    --cc=Samuel.salin@intel.com \
    --cc=aleksander.lobakin@intel.com \
    --cc=aleksandr.loktionov@intel.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=anjali.singhai@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=emil.s.tantilov@intel.com \
    --cc=horms@kernel.org \
    --cc=jayaprakash.shanmugam@intel.com \
    --cc=jgg@ziepe.ca \
    --cc=jiri@resnulli.us \
    --cc=joshua.a.hay@intel.com \
    --cc=krzysztof.czurylo@intel.com \
    --cc=kuba@kernel.org \
    --cc=larysa.zaremba@intel.com \
    --cc=leon@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=maciej.fijalkowski@intel.com \
    --cc=madhu.chittim@intel.com \
    --cc=michal.swiatkowski@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=nxne.cnse.osdt.itp.upstreaming@intel.com \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=richardcochran@gmail.com \
    --cc=sridhar.samudrala@intel.com \
    --cc=tatyana.e.nikolova@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