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: <20230426202907.2e07f031@kernel.org>
Date:   Wed, 26 Apr 2023 20:29:07 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     "Tantilov, Emil S" <emil.s.tantilov@...el.com>,
        <jesse.brandeburg@...el.com>
Cc:     <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 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?