Hi Greg,

Here are some nvmem core fixes around nvmem provider device register
and error paths.
Most of these patches have been in next for 2-3 weeks.

Am really not sure if you are taking fixes late in this cycle.
In case you are not could you please apply them for 6.3

Thanks,
Srini

Jiasheng Jiang (1):
  nvmem: brcm_nvram: Add check for kzalloc

Johan Hovold (1):
  nvmem: qcom-spmi-sdam: fix module autoloading

Michael Walle (2):
  nvmem: core: fix device node refcounting
  nvmem: core: fix cell removal on error

Russell King (Oracle) (5):
  nvmem: core: initialise nvmem->id early
  nvmem: core: remove nvmem_config wp_gpio
  nvmem: core: fix cleanup after dev_set_name()
  nvmem: core: fix registration vs use race
  nvmem: core: fix return value

Samuel Holland (1):
  nvmem: sunxi_sid: Always use 32-bit MMIO reads

 drivers/nvmem/brcm_nvram.c     |  3 ++
 drivers/nvmem/core.c           | 60 +++++++++++++++++-----------------
 drivers/nvmem/qcom-spmi-sdam.c |  1 +
 drivers/nvmem/sunxi_sid.c      | 15 ++++++++-
 include/linux/nvmem-provider.h |  2 --
 5 files changed, 48 insertions(+), 33 deletions(-)

-- 
2.25.1

On Fri, Jan 27, 2023 at 10:40:05AM +0000, Srinivas Kandagatla wrote:
> Hi Greg,
> 
> Here are some nvmem core fixes around nvmem provider device register
> and error paths.
> Most of these patches have been in next for 2-3 weeks.
> 
> Am really not sure if you are taking fixes late in this cycle.
> In case you are not could you please apply them for 6.3

When I apply them, I get the following errors from the scripts:

Commit: 36f5dbea16ad ("nvmem: core: fix return value")
	Fixes tag: Fixes: 60c8b4aebd8e ("nvmem: core: fix cleanup after dev_set_name()")
	Has these problem(s):
		- Target SHA1 does not exist
Commit: 7de8892c0527 ("nvmem: core: fix device node refcounting")
	Fixes tag: Fixes: 69aba7948cbe("nvmem: Add a simple NVMEM framework for consumers")
	Has these problem(s):
		- missing space between the SHA1 and the subject

The first one is because you have your own git tree, that's fine.  But the
second one should have given you an error when it was in linux-next, what
happened?

Let me see if I can fix this up...

greg k-h

Thanks Greg,

On 28/01/2023 13:39, Greg KH wrote:
> On Fri, Jan 27, 2023 at 10:40:05AM +0000, Srinivas Kandagatla wrote:
>> Hi Greg,
>>
>> Here are some nvmem core fixes around nvmem provider device register
>> and error paths.
>> Most of these patches have been in next for 2-3 weeks.
>>
>> Am really not sure if you are taking fixes late in this cycle.
>> In case you are not could you please apply them for 6.3
> 
> When I apply them, I get the following errors from the scripts:
> 
> Commit: 36f5dbea16ad ("nvmem: core: fix return value")
> 	Fixes tag: Fixes: 60c8b4aebd8e ("nvmem: core: fix cleanup after dev_set_name()")
> 	Has these problem(s):
> 		- Target SHA1 does not exist
> Commit: 7de8892c0527 ("nvmem: core: fix device node refcounting")
> 	Fixes tag: Fixes: 69aba7948cbe("nvmem: Add a simple NVMEM framework for consumers")
> 	Has these problem(s):
> 		- missing space between the SHA1 and the subject
> 
> The first one is because you have your own git tree, that's fine.  But the
> second one should have given you an error when it was in linux-next, what
> happened?
> 
> Let me see if I can fix this up...

Thankyou very much for fixing this up before applying, will take extra 
care next time. :-)

thanks,
srini
> 
> greg k-h