netdev - Re: [PATCH V1 net-next 6/8] net: ena: enable support of rss hash key and function changes

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] [day] [month] [year] [list]

Message-ID: <20200714085918.5e8f8a97@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date:   Tue, 14 Jul 2020 08:59:18 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     "Kiyanovski, Arthur" <akiyano@...zon.com>
Cc:     "Machulsky, Zorik" <zorik@...zon.com>,
        "davem@...emloft.net" <davem@...emloft.net>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "Woodhouse, David" <dwmw@...zon.co.uk>,
        "Matushevsky, Alexander" <matua@...zon.com>,
        "Bshara, Saeed" <saeedb@...zon.com>,
        "Wilson, Matt" <msw@...zon.com>,
        "Liguori, Anthony" <aliguori@...zon.com>,
        "Bshara, Nafea" <nafea@...zon.com>,
        "Tzalik, Guy" <gtzalik@...zon.com>,
        "Belgazal, Netanel" <netanel@...zon.com>,
        "Saidi, Ali" <alisaidi@...zon.com>,
        "Herrenschmidt, Benjamin" <benh@...zon.com>,
        "Dagan, Noam" <ndagan@...zon.com>,
        "Agroskin, Shay" <shayagr@...zon.com>,
        "Jubran, Samih" <sameehj@...zon.com>
Subject: Re: [PATCH V1 net-next 6/8] net: ena: enable support of rss hash
 key and function changes

On Tue, 14 Jul 2020 11:20:27 +0000 Kiyanovski, Arthur wrote:
> > This commit actually enables a feature after it was fixed by previous commits,
> > therefore we thought that net-next could be a right place. But if you think it
> > should go to net, we'll go ahead and resubmit it there. Thanks for your
> > comments.  
> 
> Jakub, 
> I’ve removed the patch from v2 but it seems to me there was some
> miscommunication and IMO the correct place for the patch should be
> net-next. This feature was actually turned off until now, and this
> patch turns it on. It is not a bug fix, it is actually a feature. Do
> you have an objection to me returning this patch (with this
> explanation in the commit message) to this patchsets V3?

Sounds good, the commit message makes all the difference.