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: <781ea004-6422-470e-a7b5-9a25d602f9f9@lunn.ch>
Date: Thu, 19 Dec 2024 23:32:43 +0100
From: Andrew Lunn <andrew@...n.ch>
To: John Ousterhout <ouster@...stanford.edu>
Cc: Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org,
	pabeni@...hat.com, edumazet@...gle.com, horms@...nel.org
Subject: Re: [PATCH net-next v4 01/12] inet: homa: define user-visible API
 for Homa

> > --
> > pw-bot: cr
> 
> I'm not sure what "pw-bot: cr" means; I assume this is related to the
> "#ifdef __cplusplus" discussion above?

It is documented here:

https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html#updating-patch-status

although the documentation spells it out in full, but the patchworks
bot understands a few abbreviations like cr for change-request.

Marking a patchset as changes-requested will drop it out of the list
of patches waiting to be merged, so included it at the end of a review
comment can save the Maintainers some time.

	Andrew

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ