netdev - Re: [PATCH net-next 0/1] [pull request] iwl-next Intel Wired LAN Driver Updates 2022-02-07

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]

Date:   Wed, 9 Feb 2022 17:22:32 +0000
From:   "Nguyen, Anthony L" <anthony.l.nguyen@...el.com>
To:     "leon@...nel.org" <leon@...nel.org>
CC:     "jgg@...dia.com" <jgg@...dia.com>,
        "linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
        "davem@...emloft.net" <davem@...emloft.net>,
        "Ismail, Mustafa" <mustafa.ismail@...el.com>,
        "Saleem, Shiraz" <shiraz.saleem@...el.com>,
        "Ertman, David M" <david.m.ertman@...el.com>,
        "kuba@...nel.org" <kuba@...nel.org>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH net-next 0/1] [pull request] iwl-next Intel Wired LAN
 Driver Updates 2022-02-07

On Wed, 2022-02-09 at 11:50 +0200, Leon Romanovsky wrote:
> On Tue, Feb 08, 2022 at 09:18:36PM +0000, Nguyen, Anthony L wrote:
> > On Tue, 2022-02-08 at 13:00 -0400, Jason Gunthorpe wrote:
> > > On Mon, Feb 07, 2022 at 03:59:20PM -0800, Tony Nguyen wrote:
> > > 
> 
> It means that sometimes both netdev and RDMA patches will be there,
> however such situation is not common flow. Most of the time, you will
> put only netdev changes there, because your driver core logic lays
> there and it is there the conflicts will be.
> 
> However, there are minimal set of rules which you should follow:
> 1. This branch should be based on clean -rcX. No back merge of net-
> next
> or rdma-next or other -next.
> 2. Bisectable
> 3. Possible to pull as a standlone set without extra patches on top
> and it won't break compilation and/or working target which pulled
> this
> branch.

This helps. Thanks for the information Leon.

- Tony