netdev - Re: [net-next v3 00/15] Introduce Intel IDPF driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20230502192024.28029188@kernel.org>
Date: Tue, 2 May 2023 19:20:24 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Jesse Brandeburg <jesse.brandeburg@...el.com>
Cc: "Tantilov, Emil S" <emil.s.tantilov@...el.com>,
 <intel-wired-lan@...ts.osuosl.org>, <netdev@...r.kernel.org>,
 <joshua.a.hay@...el.com>, <sridhar.samudrala@...el.com>,
 <anthony.l.nguyen@...el.com>, <willemb@...gle.com>, <decot@...gle.com>,
 <pabeni@...hat.com>, <edumazet@...gle.com>, <davem@...emloft.net>,
 <alan.brady@...el.com>, <madhu.chittim@...el.com>,
 <phani.r.burra@...el.com>, <shailendra.bhatnagar@...el.com>,
 <pavan.kumar.linga@...el.com>, <shannon.nelson@....com>,
 <simon.horman@...igine.com>, <leon@...nel.org>
Subject: Re: [net-next v3 00/15] Introduce Intel IDPF driver

On Thu, 27 Apr 2023 15:23:12 -0700 Jesse Brandeburg wrote:
> > 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?  
> 
> Sorry for the thrash on this one.
> 
> We have a proposal by doing these two things in the future:
> 1) to: intel-wired-lan, cc: netdev until we've addressed review comments
> 2) use [iwl-next ] or [iwl-net] in the Subject: when reviewing on
> intel-wired-lan, and cc:netdev, to make clear the intent in both headers
> and Subject line.
> 
> There are two discussions here
> 1) we can solve the "net-next subject" vs cc:netdev via my proposal
> above, would appreciate your feedback.
> 2) Long term, this driver will join the "normal flow" of individual
> patch series that are sent to intel-wired-lan and cc:netdev, but I'd
> like those that are sent from Intel non-maintainers to always use
> [iwl-next], [iwl-net], and Tony or I will provide series to:
> maintainers, cc:netdev with the Subject: [net-next] or [net]

Sounds like a good scheme, let's try it!
Thanks!