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, 2 Dec 2020 12:37:52 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     Saeed Mahameed <saeed@...nel.org>
Cc:     "David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: [pull request][net-next 00/15] mlx5 updates 2020-12-01

On Wed, 02 Dec 2020 12:15:15 -0800 Saeed Mahameed wrote:
> On Wed, 2020-12-02 at 11:20 -0800, Jakub Kicinski wrote:
> > To be clear - I'm asking you to send a PR for the pre-reqs and then
> > send the ethernet patches. So that the pre-reqs are in the tree
> > already
> > by the time the ethernet patches hit the ML. I thought that's what
> > you
> > did in the past, but either way it'd make my life easier.  
> 
> Ok, Done, will submit two separate pull requests.
> 
> But to avoid any wait and to create full visibility, is there a way to
> let the CI bot understand dependency between two separate pull requests
> ? or the base-commit of a pull request ?

Possibly it's just a python script (available on GH). 

Although we don't allow people to queue up multiple series which 
are co-dependent, I'm not sure if using PRs changes that much.
There still needs to be a reasonable rate control on number of patches
for example.

> I would like to send everything in one shot for full visibility.

Hm, not sure what you mean by visibility.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ