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: <20231215084924.40b47a7e@kernel.org>
Date: Fri, 15 Dec 2023 08:49:24 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Alexander Lobakin <aleksander.lobakin@...el.com>
Cc: <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
 <pabeni@...hat.com>, Marcin Szycik <marcin.szycik@...ux.intel.com>, Tony
 Nguyen <anthony.l.nguyen@...el.com>, <michal.swiatkowski@...ux.intel.com>,
 <wojciech.drewek@...el.com>, <idosch@...dia.com>,
 <jesse.brandeburg@...el.com>, <intel-wired-lan@...ts.osuosl.org>,
 <netdev@...r.kernel.org>, <jiri@...nulli.us>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v4 0/7] Add PFCP filter
 support

On Fri, 15 Dec 2023 11:11:23 +0100 Alexander Lobakin wrote:
> Ping? :s
> Or should we resubmit?

Can you wait for next merge window instead?
We're getting flooded with patches as everyone seemingly tries to get
their own (i.e. the most important!) work merged before the end of 
the year. The set of PRs from the bitmap tree which Linus decided
not to pull is not empty. So we'd have to go figure out what's exactly
is in that branch we're supposed to pull, and whether it's fine.
It probably is, but you see, this is a problem which can be solved by
waiting, and letting Linus pull it himself. While the 150 patches we're
getting a day now have to be looked at.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ