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: <20240813-mysterious-meerkat-of-gaiety-28dee9@lemur>
Date: Tue, 13 Aug 2024 11:50:53 -0400
From: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Zijun Hu <zijun_hu@...oud.com>, 
	"Rafael J. Wysocki" <rafael@...nel.org>, linux-kernel@...r.kernel.org, Zijun Hu <quic_zijuhu@...cinc.com>
Subject: Re: [PATCH v2] driver core: Simplify driver API
 device_find_child_by_name() implementation

On Tue, Aug 13, 2024 at 11:41:50AM GMT, Greg Kroah-Hartman wrote:
> > prerequisite-patch-id: f58374cebf0ada070fc0825736424dd177e49676
> 
> As those ids are not going to be in my tree (or anyone else's), how are
> we supposed to apply this?

Greg, these are patch-ids, not commit ID's -- b4 will pull them in
automatically from lore and apply on top of the base-commit specified before
applying the series.

Regards,
-K

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ