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] [day] [month] [year] [list]
Date:   Thu, 20 Sep 2018 15:06:12 +0200
From:   Bartosz Golaszewski <brgl@...ev.pl>
To:     Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Bartosz Golaszewski <bgolaszewski@...libre.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Devang Panchal <devang.panchal@...tnautics.com>,
        "Gustavo A . R . Silva" <gustavo@...eddedor.com>,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        Boris Brezillon <boris.brezillon@...tlin.com>,
        Rob Herring <robh@...nel.org>, Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH v2 0/2] eeprom: use devres for nvmem providers

2018-09-12 10:04 GMT+02:00 Bartosz Golaszewski <brgl@...ev.pl>:
> From: Bartosz Golaszewski <bgolaszewski@...libre.com>
>
> While working on the nvmem framework recently I noticed that there are
> many providers that don't use the devm variant of nvmem_register().
> This series contains relevant updates for eeprom drivers.
>
> Note that these patches are independent from my other nvmem series[1].
>
> [1] https://lkml.org/lkml/2018/9/12/265
>
> v1 -> v2:
> - fix an invalid devm_ free in patch 1
>
> Bartosz Golaszewski (2):
>   eeprom: eeprom_93xx46: use resource management
>   eeprom: at25: use devm_nvmem_register()
>
>  drivers/misc/eeprom/at25.c          |  3 +--
>  drivers/misc/eeprom/eeprom_93xx46.c | 19 +++++--------------
>  2 files changed, 6 insertions(+), 16 deletions(-)
>
> --
> 2.18.0
>

Srinivas,

Greg will probably be busy this cycle, so in case he misses those -
can you send them together with your nvmem pull request? They don't
depend on my other series in any way.

Bart

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ