From: Jakub Kicinski <kuba@kernel.org>
To: "Tantilov, Emil S" <emil.s.tantilov@intel.com>,
<jesse.brandeburg@intel.com>
Cc: willemb@google.com, pabeni@redhat.com, leon@kernel.org,
shailendra.bhatnagar@intel.com, netdev@vger.kernel.org,
edumazet@google.com, anthony.l.nguyen@intel.com,
simon.horman@corigine.com, intel-wired-lan@lists.osuosl.org,
phani.r.burra@intel.com, decot@google.com, davem@davemloft.net,
shannon.nelson@amd.com
Subject: Re: [Intel-wired-lan] [net-next v3 00/15] Introduce Intel IDPF driver
Date: Wed, 26 Apr 2023 20:29:07 -0700 [thread overview]
Message-ID: <20230426202907.2e07f031@kernel.org> (raw)
In-Reply-To: <97f635bf-a793-7d10-9a5e-2847816dda1d@intel.com>
On Wed, 26 Apr 2023 19:55:06 -0700 Tantilov, Emil S wrote:
> The v3 series are primarily for review on IWL (to intel-wired-lan,
> netdev cc-ed) as follow up for the feedback we received on v2.
Well, you put net-next in the subject.
> Was I not supposed to cc netdev in the quiet period?
That's what you got from my previous email? Did you read it?
The answer was there :|
The community volunteers can't be expected to help teach every team of
every vendor the process. That doesn't scale and leads to maintainer
frustration. You have a team at Intel which is strongly engaged
upstream (Jesse, Jake K, Maciej F, Alex L, Tony etc.) - I'd much rather
interface with them.
Jesse, does it sound workable to you? What do you have in mind in terms
of the process long term if/once this driver gets merged?
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: "Tantilov, Emil S" <emil.s.tantilov@intel.com>,
<jesse.brandeburg@intel.com>
Cc: <intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
<joshua.a.hay@intel.com>, <sridhar.samudrala@intel.com>,
<anthony.l.nguyen@intel.com>, <willemb@google.com>,
<decot@google.com>, <pabeni@redhat.com>, <edumazet@google.com>,
<davem@davemloft.net>, <alan.brady@intel.com>,
<madhu.chittim@intel.com>, <phani.r.burra@intel.com>,
<shailendra.bhatnagar@intel.com>, <pavan.kumar.linga@intel.com>,
<shannon.nelson@amd.com>, <simon.horman@corigine.com>,
<leon@kernel.org>
Subject: Re: [net-next v3 00/15] Introduce Intel IDPF driver
Date: Wed, 26 Apr 2023 20:29:07 -0700 [thread overview]
Message-ID: <20230426202907.2e07f031@kernel.org> (raw)
In-Reply-To: <97f635bf-a793-7d10-9a5e-2847816dda1d@intel.com>
On Wed, 26 Apr 2023 19:55:06 -0700 Tantilov, Emil S wrote:
> The v3 series are primarily for review on IWL (to intel-wired-lan,
> netdev cc-ed) as follow up for the feedback we received on v2.
Well, you put net-next in the subject.
> Was I not supposed to cc netdev in the quiet period?
That's what you got from my previous email? Did you read it?
The answer was there :|
The community volunteers can't be expected to help teach every team of
every vendor the process. That doesn't scale and leads to maintainer
frustration. You have a team at Intel which is strongly engaged
upstream (Jesse, Jake K, Maciej F, Alex L, Tony etc.) - I'd much rather
interface with them.
Jesse, does it sound workable to you? What do you have in mind in terms
of the process long term if/once this driver gets merged?
next prev parent reply other threads:[~2023-04-27 3:29 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 2:09 [Intel-wired-lan] [net-next v3 00/15] Introduce Intel IDPF driver Emil Tantilov
2023-04-27 2:09 ` Emil Tantilov
2023-04-27 2:09 ` [Intel-wired-lan] [net-next v3 01/15] virtchnl: add virtchnl version 2 ops Emil Tantilov
2023-04-27 2:09 ` Emil Tantilov
2023-04-27 22:04 ` [Intel-wired-lan] " Shannon Nelson
2023-04-27 22:04 ` Shannon Nelson
2023-04-28 23:10 ` [Intel-wired-lan] " Tantilov, Emil S
2023-04-28 23:10 ` Tantilov, Emil S
2023-04-27 2:09 ` [Intel-wired-lan] [net-next v3 02/15] idpf: add module register and probe functionality Emil Tantilov
2023-04-27 2:09 ` Emil Tantilov
2023-04-27 23:24 ` [Intel-wired-lan] " Shannon Nelson
2023-04-27 23:24 ` Shannon Nelson
2023-04-28 23:05 ` [Intel-wired-lan] " Tantilov, Emil S
2023-04-28 23:05 ` Tantilov, Emil S
2023-04-27 2:09 ` [Intel-wired-lan] [net-next v3 03/15] idpf: add controlq init and reset checks Emil Tantilov
2023-04-27 2:09 ` Emil Tantilov
2023-04-28 17:16 ` [Intel-wired-lan] " Shannon Nelson
2023-04-28 17:16 ` Shannon Nelson
2023-04-28 22:38 ` [Intel-wired-lan] " Tantilov, Emil S
2023-04-28 22:38 ` Tantilov, Emil S
2023-04-27 2:09 ` [Intel-wired-lan] [net-next v3 04/15] idpf: add core init and interrupt request Emil Tantilov
2023-04-27 2:09 ` Emil Tantilov
2023-04-28 19:50 ` [Intel-wired-lan] " Shannon Nelson
2023-04-28 19:50 ` Shannon Nelson
2023-04-28 21:17 ` [Intel-wired-lan] " Tantilov, Emil S
2023-04-28 21:17 ` Tantilov, Emil S
2023-04-27 2:09 ` [Intel-wired-lan] [net-next v3 05/15] idpf: add create vport and netdev configuration Emil Tantilov
2023-04-27 2:09 ` Emil Tantilov
2023-04-27 2:09 ` [Intel-wired-lan] [net-next v3 06/15] idpf: continue expanding init task Emil Tantilov
2023-04-27 2:09 ` Emil Tantilov
2023-04-27 2:09 ` [Intel-wired-lan] [net-next v3 07/15] idpf: configure resources for TX queues Emil Tantilov
2023-04-27 2:09 ` Emil Tantilov
2023-04-27 2:09 ` [Intel-wired-lan] [net-next v3 08/15] idpf: configure resources for RX queues Emil Tantilov
2023-04-27 2:09 ` Emil Tantilov
2023-04-27 2:09 ` [Intel-wired-lan] [net-next v3 09/15] idpf: initialize interrupts and enable vport Emil Tantilov
2023-04-27 2:09 ` Emil Tantilov
2023-04-27 2:09 ` [Intel-wired-lan] [net-next v3 10/15] idpf: add splitq start_xmit Emil Tantilov
2023-04-27 2:09 ` Emil Tantilov
2023-04-27 2:09 ` [Intel-wired-lan] [net-next v3 11/15] idpf: add TX splitq napi poll support Emil Tantilov
2023-04-27 2:09 ` Emil Tantilov
2023-04-27 2:09 ` [Intel-wired-lan] [net-next v3 12/15] idpf: add RX " Emil Tantilov
2023-04-27 2:09 ` Emil Tantilov
2023-04-27 2:09 ` [Intel-wired-lan] [net-next v3 13/15] idpf: add singleq start_xmit and napi poll Emil Tantilov
2023-04-27 2:09 ` Emil Tantilov
2023-04-27 2:09 ` [Intel-wired-lan] [net-next v3 14/15] idpf: add ethtool callbacks Emil Tantilov
2023-04-27 2:09 ` Emil Tantilov
2023-04-27 2:09 ` [Intel-wired-lan] [net-next v3 15/15] idpf: configure SRIOV and add other ndo_ops Emil Tantilov
2023-04-27 2:09 ` Emil Tantilov
2023-04-27 2:46 ` [Intel-wired-lan] [net-next v3 00/15] Introduce Intel IDPF driver Jakub Kicinski
2023-04-27 2:46 ` Jakub Kicinski
2023-04-27 2:55 ` [Intel-wired-lan] " Tantilov, Emil S
2023-04-27 2:55 ` Tantilov, Emil S
2023-04-27 3:29 ` Jakub Kicinski [this message]
2023-04-27 3:29 ` Jakub Kicinski
2023-04-27 22:23 ` [Intel-wired-lan] " Jesse Brandeburg
2023-04-27 22:23 ` Jesse Brandeburg
2023-05-03 2:20 ` [Intel-wired-lan] " Jakub Kicinski
2023-05-03 2:20 ` Jakub Kicinski
2023-05-03 16:24 ` [Intel-wired-lan] " Jesse Brandeburg
2023-05-03 16:24 ` Jesse Brandeburg
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=20230426202907.2e07f031@kernel.org \
--to=kuba@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=decot@google.com \
--cc=edumazet@google.com \
--cc=emil.s.tantilov@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=leon@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=phani.r.burra@intel.com \
--cc=shailendra.bhatnagar@intel.com \
--cc=shannon.nelson@amd.com \
--cc=simon.horman@corigine.com \
--cc=willemb@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.