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
| ||
|
Message-ID: <20230126161002.74wbgoo7ytx4cyoi@builder.lan> Date: Thu, 26 Jan 2023 10:10:02 -0600 From: Bjorn Andersson <andersson@...nel.org> To: Johan Hovold <johan+linaro@...nel.org> Cc: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>, Andy Gross <agross@...nel.org>, Konrad Dybcio <konrad.dybcio@...aro.org>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 0/2] nvmem: qcom-spmi-sdam: fix module autoloading On Thu, Jan 26, 2023 at 02:30:32PM +0100, Johan Hovold wrote: > The Qualcomm SDAM nvme driver did not have a module device table, which > prevents userspace from autoloading the driver when built as a module. > > The driver was also being registered at subsys init time when built in > despite the fact that it can also be built as a module, which makes > little sense. There are currently no in-tree users of this driver and > there's no reason why we can't just let driver core sort out the probe > order. > > Note that this driver will be used to implement support for the PMIC RTC > on Qualcomm platforms where the time registers are read-only (sic). > > Johan > Reviewed-by: Bjorn Andersson <andersson@...nel.org> > > Johan Hovold (2): > nvmem: qcom-spmi-sdam: fix module autoloading > nvmem: qcom-spmi-sdam: register at device init time > > drivers/nvmem/qcom-spmi-sdam.c | 14 ++------------ > 1 file changed, 2 insertions(+), 12 deletions(-) > > -- > 2.39.1 >
Powered by blists - more mailing lists