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: <20240213182026.7c14d7d4@kernel.org>
Date: Tue, 13 Feb 2024 18:20:26 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Tony Nguyen <anthony.l.nguyen@...el.com>
Cc: Andrew Lunn <andrew@...n.ch>, <davem@...emloft.net>,
 <pabeni@...hat.com>, <edumazet@...gle.com>, <netdev@...r.kernel.org>, Kurt
 Kanzenbach <kurt@...utronix.de>, <sasha.neftin@...el.com>, Naama Meir
 <naamax.meir@...ux.intel.com>
Subject: Re: [PATCH net-next] igc: Add support for LEDs on i225/i226

On Tue, 13 Feb 2024 13:05:43 -0800 Tony Nguyen wrote:
> > State: Awaiting Upstream  
> 
> For Awaiting Upstream:
> 
> "
> patch should be reviewed and handled by appropriate sub-maintainer, who 
> will send it on to the networking trees; patches set to Awaiting 
> upstream in netdev's patchwork will usually remain in this state, 
> whether the sub-maintainer requested changes, accepted or rejected the patch
> "
> https://docs.kernel.org/process/maintainer-netdev.html#patch-status

FWIW I think it's one of those things where particular cases may look
odd, but for those on the patch handling path always following the same
procedure make the life *so* much easier :(

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ