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
| ||
|
Date: Fri, 27 Nov 2020 13:22:28 +0000 From: Lee Jones <lee.jones@...aro.org> To: Bartosz Golaszewski <bgolaszewski@...libre.com> Cc: Bartosz Golaszewski <brgl@...ev.pl>, Alessandro Zummo <a.zummo@...ertech.it>, Alexandre Belloni <alexandre.belloni@...tlin.com>, linux-rtc@...r.kernel.org, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 7/8] rtc: rework rtc_register_device() resource management On Fri, 27 Nov 2020, Bartosz Golaszewski wrote: > On Fri, Nov 27, 2020 at 10:16 AM Lee Jones <lee.jones@...aro.org> wrote: > > > > > > > > On Mon, 9 Nov 2020 at 16:34, Bartosz Golaszewski <brgl@...ev.pl> wrote: > >> > >> From: Bartosz Golaszewski <bgolaszewski@...libre.com> > >> > >> rtc_register_device() is a managed interface but it doesn't use devres > >> by itself - instead it marks an rtc_device as "registered" and the devres > >> callback for devm_rtc_allocate_device() takes care of resource release. > >> > >> This doesn't correspond with the design behind devres where managed > >> structures should not be aware of being managed. The correct solution > >> here is to register a separate devres callback for unregistering the > >> device. > >> > >> While at it: rename rtc_register_device() to devm_rtc_register_device() > >> and add it to the list of managed interfaces in devres.rst. This way we > >> can avoid any potential confusion of driver developers who may expect > >> there to exist a corresponding unregister function. > >> > >> Signed-off-by: Bartosz Golaszewski <bgolaszewski@...libre.com> > >> --- > >> .../driver-api/driver-model/devres.rst | 1 + > >> arch/alpha/kernel/rtc.c | 2 +- > >> drivers/mfd/menelaus.c | 2 +- > > > > > > This patch should have been sent to and Acked by MFD too. > > > > Sorry Lee, I missed the fact that there were changes outside of > drivers/rtc/. Other than skipping the MFD maintainer - do you see > anything wrong in that bit? No real harm done. The patch looks fine from an MFD standpoint. -- Lee Jones [李琼斯] Senior Technical Lead - Developer Services Linaro.org │ Open source software for Arm SoCs Follow Linaro: Facebook | Twitter | Blog
Powered by blists - more mailing lists