mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: Jiri Prchal <jiri.prchal@aksignal.cz>,
	linux-kernel@vger.kernel.org,
	 Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	stable@vger.kernel.org
Subject: Re: (subset) [PATCH 0/5] nvmem: core: one fix and several cleanups for sysfs code
Date: Sat, 22 Jun 2024 13:51:08 +0200	[thread overview]
Message-ID: <a9d4e4d7-3aa3-4d08-a90e-2c5cfe907aff@t-8ch.de> (raw)
In-Reply-To: <171905336506.244973.16113259707012674277.b4-ty@linaro.org>

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

      reply	other threads:[~2024-06-22 11:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-20 16:00 Thomas Weißschuh
2024-06-20 16:00 ` [PATCH 1/5] nvmem: core: only change name to fram for current attribute Thomas Weißschuh
2024-06-20 16:00 ` [PATCH 2/5] nvmem: core: mark bin_attr_nvmem_eeprom_compat as const Thomas Weißschuh
2024-06-20 16:00 ` [PATCH 3/5] nvmem: core: add single sysfs group Thomas Weißschuh
2024-06-20 16:00 ` [PATCH 4/5] nvmem: core: remove global nvmem_cells_group Thomas Weißschuh
2024-06-20 16:00 ` [PATCH 5/5] nvmem: core: drop unnecessary range checks in sysfs callbacks Thomas Weißschuh
2024-06-22 10:14 ` (subset) [PATCH 0/5] nvmem: core: one fix and several cleanups for sysfs code Srinivas Kandagatla
2024-06-22 10:49 ` Srinivas Kandagatla
2024-06-22 11:51   ` Thomas Weißschuh [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a9d4e4d7-3aa3-4d08-a90e-2c5cfe907aff@t-8ch.de \
    --to=linux@weissschuh.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jiri.prchal@aksignal.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®