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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <174412352089.3870554.10940173443800637826.b4-ty@bootlin.com>
Date: Tue, 8 Apr 2025 16:45:31 +0200
From: Alexandre Belloni <alexandre.belloni@...tlin.com>
To: linux-kernel@...r.kernel.org, Sudeep Holla <sudeep.holla@....com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Ard Biesheuvel <ardb@...nel.org>, linux-rtc@...r.kernel.org,
	linux-efi@...r.kernel.org
Subject: Re: (subset) [PATCH v2 4/8] rtc: efi: Transition to the faux device
 interface

On Tue, 18 Mar 2025 17:01:42 +0000, Sudeep Holla wrote:
> The EFI RTC driver does not require the creation of a platform device.
> Originally, this approach was chosen for simplicity when the driver was
> first implemented.
> 
> With the introduction of the lightweight faux device interface, we now
> have a more appropriate alternative. Migrate the driver to utilize the
> faux bus, given that the platform device it previously created was not
> a real one anyway. This will simplify the code, reducing its footprint
> while maintaining functionality.
> 
> [...]

Applied, thanks!

[4/8] rtc: efi: Transition to the faux device interface
      https://git.kernel.org/abelloni/c/89a378d01e7e

Best regards,

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ