[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a9d4e4d7-3aa3-4d08-a90e-2c5cfe907aff@t-8ch.de>
Date: Sat, 22 Jun 2024 13:51:08 +0200
From: Thomas Weißschuh <linux@...ssschuh.net>
To: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Cc: Jiri Prchal <jiri.prchal@...ignal.cz>, linux-kernel@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>, stable@...r.kernel.org
Subject: Re: (subset) [PATCH 0/5] nvmem: core: one fix and several cleanups
for sysfs code
On 2024-06-22 11:49:25+0000, Srinivas Kandagatla wrote:
> On Thu, 20 Jun 2024 18:00:32 +0200, Thomas Weißschuh wrote:
> > Patch 1 is a bugfix.
> > All other patches are small cleanups.
> >
> > Hint about another nvmem bugfix at [0].
> >
> > [0] https://lore.kernel.org/lkml/20240619-nvmem-cell-sysfs-perm-v1-1-e5b7882fdfa8@weissschuh.net/
> >
> > [...]
>
> Applied, thanks!
Thanks!
> [2/5] nvmem: core: mark bin_attr_nvmem_eeprom_compat as const
> commit: 178a9aea2c5db8328757fdea66922bda0236e95c
Please note that patch 2 has a dependency on patch 1.
In the current state this will probably lead to build errors in
linux-next, as nvmem-fixes is not part of linux-next.
I should have mentioned that.
In theory patch 2 could even be squashed into patch 1, as it really is
mostly an extension of it.
> [3/5] nvmem: core: add single sysfs group
> commit: 80026ea9fdc22bbc8bfa9b41f54baba314bacc55
> [4/5] nvmem: core: remove global nvmem_cells_group
> commit: e76590d9faf8c058df9faf0b6513f055beb84b57
> [5/5] nvmem: core: drop unnecessary range checks in sysfs callbacks
> commit: 050e51c214c5bbe5ffd9e7f5927ccdcd2da18fe3
Powered by blists - more mailing lists