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]
Date:   Mon, 8 Aug 2022 14:50:34 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     Luiz Augusto von Dentz <luiz.dentz@...il.com>
Cc:     David Miller <davem@...emloft.net>,
        "linux-bluetooth@...r.kernel.org" <linux-bluetooth@...r.kernel.org>,
        "open list:NETWORKING [GENERAL]" <netdev@...r.kernel.org>
Subject: Re: pull request: bluetooth 2022-08-05

On Mon, 8 Aug 2022 14:36:16 -0700 Luiz Augusto von Dentz wrote:
> > > Still rebasing, I thought that didn't make any difference as long as
> > > the patches apply.  
> >
> > Long term the non-rebasing model is probably better since it'd be great
> > for the bluetooth tree to be included in linux-next.  
> 
> You mean that bluetooth-next would be pulled directly into linux-next
> rather than net-next?

No, no. linux-next is just an integration tree, it doesn't take PRs.
Some more info:

https://www.kernel.org/doc/html/latest/process/howto.html#linux-next-integration-testing-tree

It's mostly for checking for conflicts and automated testing.
All the compilation bots run on it.

> > Since you haven't started using that model, tho, would you mind
> > repairing the Fixes tags in this PR? :)  
> 
> Let me fix them.

Thanks!

Powered by blists - more mailing lists