Here are some nvmem patches slightly more than usual for 6.6 that includes

- Support for NXP eFuse, qcom secure qfprom, QCM2290 nvmem providers
- core level cleanup around error handling and layout creation.
- few minor cleanups across providers drivers to use better
  apis and a typo fix.

Can you please queue them up for 6.6.

Thanks,
Srini

MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit


Atul Raut (1):
  nvmem: u-boot-env:: Replace zero-length array with
    DECLARE_FLEX_ARRAY() helper

Diederik de Haas (1):
  nvmem: Kconfig: Fix typo "drive" -> "driver"

Komal Bajaj (2):
  dt-bindings: nvmem: sec-qfprom: Add bindings for secure qfprom
  nvmem: sec-qfprom: Add Qualcomm secure QFPROM support

Konrad Dybcio (1):
  dt-bindings: nvmem: Add compatible for QCM2290

Matti Lehtimäki (1):
  dt-bindings: nvmem: qfprom: Add compatible for MSM8226

Miquel Raynal (4):
  nvmem: core: Create all cells before adding the nvmem device
  nvmem: core: Return NULL when no nvmem layout is found
  nvmem: core: Do not open-code existing functions
  nvmem: core: Notify when a new layout is registered

Rafał Miłecki (1):
  dt-bindings: nvmem: fixed-cell: add compatible for MAC cells

Richard Alpe (2):
  dt-bindings: nvmem: Add t1023-sfp efuse support
  nvmem: add new NXP QorIQ eFuse driver

Rob Herring (1):
  nvmem: Explicitly include correct DT includes

Yangtao Li (8):
  nvmem: sunxi_sid: Convert to devm_platform_ioremap_resource()
  nvmem: brcm_nvram: Use devm_platform_get_and_ioremap_resource()
  nvmem: lpc18xx_otp: Convert to devm_platform_ioremap_resource()
  nvmem: meson-mx-efuse: Convert to devm_platform_ioremap_resource()
  nvmem: rockchip-efuse: Use devm_platform_get_and_ioremap_resource()
  nvmem: stm32-romem: Use devm_platform_get_and_ioremap_resource()
  nvmem: qfprom: do some cleanup
  nvmem: uniphier: Use devm_platform_get_and_ioremap_resource()

 .../bindings/nvmem/fsl,t1023-sfp.yaml         | 37 +++++++
 .../bindings/nvmem/layouts/fixed-cell.yaml    | 26 +++++
 .../bindings/nvmem/layouts/fixed-layout.yaml  | 12 +++
 .../devicetree/bindings/nvmem/nvmem.yaml      |  5 +-
 .../bindings/nvmem/qcom,qfprom.yaml           |  2 +
 .../bindings/nvmem/qcom,sec-qfprom.yaml       | 55 +++++++++++
 drivers/nvmem/Kconfig                         | 31 +++++-
 drivers/nvmem/Makefile                        |  4 +
 drivers/nvmem/bcm-ocotp.c                     |  1 -
 drivers/nvmem/brcm_nvram.c                    |  3 +-
 drivers/nvmem/core.c                          | 19 ++--
 drivers/nvmem/imx-iim.c                       |  1 -
 drivers/nvmem/imx-ocotp-ele.c                 |  2 +-
 drivers/nvmem/imx-ocotp-scu.c                 |  2 +-
 drivers/nvmem/imx-ocotp.c                     |  1 -
 drivers/nvmem/lpc18xx_otp.c                   |  5 +-
 drivers/nvmem/meson-mx-efuse.c                |  5 +-
 drivers/nvmem/qcom-spmi-sdam.c                |  2 +-
 drivers/nvmem/qfprom.c                        | 17 +---
 drivers/nvmem/qoriq-efuse.c                   | 78 +++++++++++++++
 drivers/nvmem/rave-sp-eeprom.c                |  2 +-
 drivers/nvmem/rockchip-efuse.c                |  3 +-
 drivers/nvmem/sc27xx-efuse.c                  |  1 -
 drivers/nvmem/sec-qfprom.c                    | 97 +++++++++++++++++++
 drivers/nvmem/snvs_lpgpr.c                    |  3 +-
 drivers/nvmem/sprd-efuse.c                    |  2 +-
 drivers/nvmem/stm32-romem.c                   |  3 +-
 drivers/nvmem/sunplus-ocotp.c                 |  2 +-
 drivers/nvmem/sunxi_sid.c                     |  5 +-
 drivers/nvmem/u-boot-env.c                    |  4 +-
 drivers/nvmem/uniphier-efuse.c                |  3 +-
 include/linux/nvmem-consumer.h                |  4 +-
 32 files changed, 379 insertions(+), 58 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/nvmem/fsl,t1023-sfp.yaml
 create mode 100644 Documentation/devicetree/bindings/nvmem/qcom,sec-qfprom.yaml
 create mode 100644 drivers/nvmem/qoriq-efuse.c
 create mode 100644 drivers/nvmem/sec-qfprom.c

-- 
2.25.1

On Mon, Aug 14, 2023 at 05:52:30PM +0100, Srinivas Kandagatla wrote:
> Here are some nvmem patches slightly more than usual for 6.6 that includes
> 
> - Support for NXP eFuse, qcom secure qfprom, QCM2290 nvmem providers
> - core level cleanup around error handling and layout creation.
> - few minor cleanups across providers drivers to use better
>   apis and a typo fix.
> 
> Can you please queue them up for 6.6.

I did, thanks, but your email system needs to be fixed:

 Link: https://lore.kernel.org/r/20230818124338.37880-1-yuehaibing@huawei.com
 Base: applies clean to current tree
       git checkout -b 20230818_yuehaibing_huawei_com HEAD
Applying: greybus: svc: Remove unused declarations
Press any key to continue...
Grabbing thread from lore.kernel.org/all/20230814165252.93422-1-srinivas.kandagatla@linaro.org/t.mbox.gz
Analyzing 23 messages in the thread
Checking attestation on all messages, may take a moment...
---
  ✗ [PATCH 1/22] dt-bindings: nvmem: fixed-cell: add compatible for MAC cells
  ✗ [PATCH 2/22] nvmem: sunxi_sid: Convert to devm_platform_ioremap_resource()
  ✗ [PATCH 3/22] nvmem: brcm_nvram: Use devm_platform_get_and_ioremap_resource()
  ✗ [PATCH 4/22] nvmem: lpc18xx_otp: Convert to devm_platform_ioremap_resource()
  ✗ [PATCH 5/22] nvmem: meson-mx-efuse: Convert to devm_platform_ioremap_resource()
  ✗ [PATCH 6/22] nvmem: rockchip-efuse: Use devm_platform_get_and_ioremap_resource()
  ✗ [PATCH 7/22] nvmem: stm32-romem: Use devm_platform_get_and_ioremap_resource()
  ✗ [PATCH 8/22] nvmem: qfprom: do some cleanup
  ✗ [PATCH 9/22] nvmem: uniphier: Use devm_platform_get_and_ioremap_resource()
  ✗ [PATCH 10/22] dt-bindings: nvmem: qfprom: Add compatible for MSM8226
  ✗ [PATCH 11/22] dt-bindings: nvmem: Add t1023-sfp efuse support
  ✗ [PATCH 12/22] nvmem: add new NXP QorIQ eFuse driver
  ✗ [PATCH 13/22] nvmem: Explicitly include correct DT includes
  ✗ [PATCH 14/22] nvmem: Kconfig: Fix typo "drive" -> "driver"
  ✗ [PATCH 15/22] dt-bindings: nvmem: Add compatible for QCM2290
  ✗ [PATCH 16/22] dt-bindings: nvmem: sec-qfprom: Add bindings for secure qfprom
  ✗ [PATCH 17/22] nvmem: sec-qfprom: Add Qualcomm secure QFPROM support
  ✗ [PATCH 18/22] nvmem: u-boot-env:: Replace zero-length array with DECLARE_FLEX_ARRAY() helper
  ✗ [PATCH 19/22] nvmem: core: Create all cells before adding the nvmem device
  ✗ [PATCH 20/22] nvmem: core: Return NULL when no nvmem layout is found
  ✗ [PATCH 21/22] nvmem: core: Do not open-code existing functions
  ✗ [PATCH 22/22] nvmem: core: Notify when a new layout is registered
  ---
  ✗ BADSIG: DKIM/linaro.org

On 22/08/2023 15:34, Greg KH wrote:
> On Mon, Aug 14, 2023 at 05:52:30PM +0100, Srinivas Kandagatla wrote:
>> Here are some nvmem patches slightly more than usual for 6.6 that includes
>>
>> - Support for NXP eFuse, qcom secure qfprom, QCM2290 nvmem providers
>> - core level cleanup around error handling and layout creation.
>> - few minor cleanups across providers drivers to use better
>>    apis and a typo fix.
>>
>> Can you please queue them up for 6.6.
> 
> I did, thanks, but your email system needs to be fixed:


Do you mean Attestation failing part or something else?

--srini
> 
>   Link: https://lore.kernel.org/r/20230818124338.37880-1-yuehaibing@huawei.com
>   Base: applies clean to current tree
>         git checkout -b 20230818_yuehaibing_huawei_com HEAD
> Applying: greybus: svc: Remove unused declarations
> Press any key to continue...
> Grabbing thread from lore.kernel.org/all/20230814165252.93422-1-srinivas.kandagatla@linaro.org/t.mbox.gz
> Analyzing 23 messages in the thread
> Checking attestation on all messages, may take a moment...
> ---
>    ✗ [PATCH 1/22] dt-bindings: nvmem: fixed-cell: add compatible for MAC cells
>    ✗ [PATCH 2/22] nvmem: sunxi_sid: Convert to devm_platform_ioremap_resource()
>    ✗ [PATCH 3/22] nvmem: brcm_nvram: Use devm_platform_get_and_ioremap_resource()
>    ✗ [PATCH 4/22] nvmem: lpc18xx_otp: Convert to devm_platform_ioremap_resource()
>    ✗ [PATCH 5/22] nvmem: meson-mx-efuse: Convert to devm_platform_ioremap_resource()
>    ✗ [PATCH 6/22] nvmem: rockchip-efuse: Use devm_platform_get_and_ioremap_resource()
>    ✗ [PATCH 7/22] nvmem: stm32-romem: Use devm_platform_get_and_ioremap_resource()
>    ✗ [PATCH 8/22] nvmem: qfprom: do some cleanup
>    ✗ [PATCH 9/22] nvmem: uniphier: Use devm_platform_get_and_ioremap_resource()
>    ✗ [PATCH 10/22] dt-bindings: nvmem: qfprom: Add compatible for MSM8226
>    ✗ [PATCH 11/22] dt-bindings: nvmem: Add t1023-sfp efuse support
>    ✗ [PATCH 12/22] nvmem: add new NXP QorIQ eFuse driver
>    ✗ [PATCH 13/22] nvmem: Explicitly include correct DT includes
>    ✗ [PATCH 14/22] nvmem: Kconfig: Fix typo "drive" -> "driver"
>    ✗ [PATCH 15/22] dt-bindings: nvmem: Add compatible for QCM2290
>    ✗ [PATCH 16/22] dt-bindings: nvmem: sec-qfprom: Add bindings for secure qfprom
>    ✗ [PATCH 17/22] nvmem: sec-qfprom: Add Qualcomm secure QFPROM support
>    ✗ [PATCH 18/22] nvmem: u-boot-env:: Replace zero-length array with DECLARE_FLEX_ARRAY() helper
>    ✗ [PATCH 19/22] nvmem: core: Create all cells before adding the nvmem device
>    ✗ [PATCH 20/22] nvmem: core: Return NULL when no nvmem layout is found
>    ✗ [PATCH 21/22] nvmem: core: Do not open-code existing functions
>    ✗ [PATCH 22/22] nvmem: core: Notify when a new layout is registered
>    ---
>    ✗ BADSIG: DKIM/linaro.org

On Tue, Aug 22, 2023 at 06:29:54PM +0100, Srinivas Kandagatla wrote:
> 
> 
> On 22/08/2023 15:34, Greg KH wrote:
> > On Mon, Aug 14, 2023 at 05:52:30PM +0100, Srinivas Kandagatla wrote:
> > > Here are some nvmem patches slightly more than usual for 6.6 that includes
> > > 
> > > - Support for NXP eFuse, qcom secure qfprom, QCM2290 nvmem providers
> > > - core level cleanup around error handling and layout creation.
> > > - few minor cleanups across providers drivers to use better
> > >    apis and a typo fix.
> > > 
> > > Can you please queue them up for 6.6.
> > 
> > I did, thanks, but your email system needs to be fixed:
> 
> 
> Do you mean Attestation failing part or something else?

Yes:

> >   Link: https://lore.kernel.org/r/20230818124338.37880-1-yuehaibing@huawei.com
> >   Base: applies clean to current tree
> >         git checkout -b 20230818_yuehaibing_huawei_com HEAD
> > Applying: greybus: svc: Remove unused declarations
> > Press any key to continue...
> > Grabbing thread from lore.kernel.org/all/20230814165252.93422-1-srinivas.kandagatla@linaro.org/t.mbox.gz
> > Analyzing 23 messages in the thread
> > Checking attestation on all messages, may take a moment...
> > ---
> >    ✗ [PATCH 1/22] dt-bindings: nvmem: fixed-cell: add compatible for MAC cells
> >    ✗ [PATCH 2/22] nvmem: sunxi_sid: Convert to devm_platform_ioremap_resource()
> >    ✗ [PATCH 3/22] nvmem: brcm_nvram: Use devm_platform_get_and_ioremap_resource()
> >    ✗ [PATCH 4/22] nvmem: lpc18xx_otp: Convert to devm_platform_ioremap_resource()
> >    ✗ [PATCH 5/22] nvmem: meson-mx-efuse: Convert to devm_platform_ioremap_resource()
> >    ✗ [PATCH 6/22] nvmem: rockchip-efuse: Use devm_platform_get_and_ioremap_resource()
> >    ✗ [PATCH 7/22] nvmem: stm32-romem: Use devm_platform_get_and_ioremap_resource()
> >    ✗ [PATCH 8/22] nvmem: qfprom: do some cleanup
> >    ✗ [PATCH 9/22] nvmem: uniphier: Use devm_platform_get_and_ioremap_resource()
> >    ✗ [PATCH 10/22] dt-bindings: nvmem: qfprom: Add compatible for MSM8226
> >    ✗ [PATCH 11/22] dt-bindings: nvmem: Add t1023-sfp efuse support
> >    ✗ [PATCH 12/22] nvmem: add new NXP QorIQ eFuse driver
> >    ✗ [PATCH 13/22] nvmem: Explicitly include correct DT includes
> >    ✗ [PATCH 14/22] nvmem: Kconfig: Fix typo "drive" -> "driver"
> >    ✗ [PATCH 15/22] dt-bindings: nvmem: Add compatible for QCM2290
> >    ✗ [PATCH 16/22] dt-bindings: nvmem: sec-qfprom: Add bindings for secure qfprom
> >    ✗ [PATCH 17/22] nvmem: sec-qfprom: Add Qualcomm secure QFPROM support
> >    ✗ [PATCH 18/22] nvmem: u-boot-env:: Replace zero-length array with DECLARE_FLEX_ARRAY() helper
> >    ✗ [PATCH 19/22] nvmem: core: Create all cells before adding the nvmem device
> >    ✗ [PATCH 20/22] nvmem: core: Return NULL when no nvmem layout is found
> >    ✗ [PATCH 21/22] nvmem: core: Do not open-code existing functions
> >    ✗ [PATCH 22/22] nvmem: core: Notify when a new layout is registered
> >    ---
> >    ✗ BADSIG: DKIM/linaro.org

Looks like someone is impersonating you, or Linaro's email server is
broken?  I think other Linaro emails validate properly, so is this
something with your setup?

thanks,

greg k-h

On 22/08/2023 18:37, Greg KH wrote:
> On Tue, Aug 22, 2023 at 06:29:54PM +0100, Srinivas Kandagatla wrote:
>>
>>
>> On 22/08/2023 15:34, Greg KH wrote:
>>> On Mon, Aug 14, 2023 at 05:52:30PM +0100, Srinivas Kandagatla wrote:
>>>> Here are some nvmem patches slightly more than usual for 6.6 that includes
>>>>
>>>> - Support for NXP eFuse, qcom secure qfprom, QCM2290 nvmem providers
>>>> - core level cleanup around error handling and layout creation.
>>>> - few minor cleanups across providers drivers to use better
>>>>     apis and a typo fix.
>>>>
>>>> Can you please queue them up for 6.6.
>>>
>>> I did, thanks, but your email system needs to be fixed:
>>
>>
>> Do you mean Attestation failing part or something else?
> 
> Yes:
> 
I did not setup patatt in my workflow yet, which is why this is failing 
attestation.
will do that before sending out v2.

thanks,
srini

>>>    Link: https://lore.kernel.org/r/20230818124338.37880-1-yuehaibing@huawei.com
>>>    Base: applies clean to current tree
>>>          git checkout -b 20230818_yuehaibing_huawei_com HEAD
>>> Applying: greybus: svc: Remove unused declarations
>>> Press any key to continue...
>>> Grabbing thread from lore.kernel.org/all/20230814165252.93422-1-srinivas.kandagatla@linaro.org/t.mbox.gz
>>> Analyzing 23 messages in the thread
>>> Checking attestation on all messages, may take a moment...
>>> ---
>>>     ✗ [PATCH 1/22] dt-bindings: nvmem: fixed-cell: add compatible for MAC cells
>>>     ✗ [PATCH 2/22] nvmem: sunxi_sid: Convert to devm_platform_ioremap_resource()
>>>     ✗ [PATCH 3/22] nvmem: brcm_nvram: Use devm_platform_get_and_ioremap_resource()
>>>     ✗ [PATCH 4/22] nvmem: lpc18xx_otp: Convert to devm_platform_ioremap_resource()
>>>     ✗ [PATCH 5/22] nvmem: meson-mx-efuse: Convert to devm_platform_ioremap_resource()
>>>     ✗ [PATCH 6/22] nvmem: rockchip-efuse: Use devm_platform_get_and_ioremap_resource()
>>>     ✗ [PATCH 7/22] nvmem: stm32-romem: Use devm_platform_get_and_ioremap_resource()
>>>     ✗ [PATCH 8/22] nvmem: qfprom: do some cleanup
>>>     ✗ [PATCH 9/22] nvmem: uniphier: Use devm_platform_get_and_ioremap_resource()
>>>     ✗ [PATCH 10/22] dt-bindings: nvmem: qfprom: Add compatible for MSM8226
>>>     ✗ [PATCH 11/22] dt-bindings: nvmem: Add t1023-sfp efuse support
>>>     ✗ [PATCH 12/22] nvmem: add new NXP QorIQ eFuse driver
>>>     ✗ [PATCH 13/22] nvmem: Explicitly include correct DT includes
>>>     ✗ [PATCH 14/22] nvmem: Kconfig: Fix typo "drive" -> "driver"
>>>     ✗ [PATCH 15/22] dt-bindings: nvmem: Add compatible for QCM2290
>>>     ✗ [PATCH 16/22] dt-bindings: nvmem: sec-qfprom: Add bindings for secure qfprom
>>>     ✗ [PATCH 17/22] nvmem: sec-qfprom: Add Qualcomm secure QFPROM support
>>>     ✗ [PATCH 18/22] nvmem: u-boot-env:: Replace zero-length array with DECLARE_FLEX_ARRAY() helper
>>>     ✗ [PATCH 19/22] nvmem: core: Create all cells before adding the nvmem device
>>>     ✗ [PATCH 20/22] nvmem: core: Return NULL when no nvmem layout is found
>>>     ✗ [PATCH 21/22] nvmem: core: Do not open-code existing functions
>>>     ✗ [PATCH 22/22] nvmem: core: Notify when a new layout is registered
>>>     ---
>>>     ✗ BADSIG: DKIM/linaro.org
> 
> Looks like someone is impersonating you, or Linaro's email server is
> broken?  I think other Linaro emails validate properly, so is this
> something with your setup?
> 
> thanks,
> 
> greg k-h

On Wed, Aug 23, 2023 at 09:54:04AM +0100, Srinivas Kandagatla wrote:
> 
> 
> On 22/08/2023 18:37, Greg KH wrote:
> > On Tue, Aug 22, 2023 at 06:29:54PM +0100, Srinivas Kandagatla wrote:
> > > 
> > > 
> > > On 22/08/2023 15:34, Greg KH wrote:
> > > > On Mon, Aug 14, 2023 at 05:52:30PM +0100, Srinivas Kandagatla wrote:
> > > > > Here are some nvmem patches slightly more than usual for 6.6 that includes
> > > > > 
> > > > > - Support for NXP eFuse, qcom secure qfprom, QCM2290 nvmem providers
> > > > > - core level cleanup around error handling and layout creation.
> > > > > - few minor cleanups across providers drivers to use better
> > > > >     apis and a typo fix.
> > > > > 
> > > > > Can you please queue them up for 6.6.
> > > > 
> > > > I did, thanks, but your email system needs to be fixed:
> > > 
> > > 
> > > Do you mean Attestation failing part or something else?
> > 
> > Yes:
> > 
> I did not setup patatt in my workflow yet, which is why this is failing
> attestation.

No, this is not for patatt (which would be good to have, I agree.)  This
is due to Linaro, or you, not setting up DKIM properly.

As this works for other Linaro developers, you might want to ask them
how they resolved it.

thanks,

greg k-h

On 23/08/2023 09:59, Greg KH wrote:
> On Wed, Aug 23, 2023 at 09:54:04AM +0100, Srinivas Kandagatla wrote:
>>
>>
>> On 22/08/2023 18:37, Greg KH wrote:
>>> On Tue, Aug 22, 2023 at 06:29:54PM +0100, Srinivas Kandagatla wrote:
>>>>
>>>>
>>>> On 22/08/2023 15:34, Greg KH wrote:
>>>>> On Mon, Aug 14, 2023 at 05:52:30PM +0100, Srinivas Kandagatla wrote:
>>>>>> Here are some nvmem patches slightly more than usual for 6.6 that includes
>>>>>>
>>>>>> - Support for NXP eFuse, qcom secure qfprom, QCM2290 nvmem providers
>>>>>> - core level cleanup around error handling and layout creation.
>>>>>> - few minor cleanups across providers drivers to use better
>>>>>>      apis and a typo fix.
>>>>>>
>>>>>> Can you please queue them up for 6.6.
>>>>>
>>>>> I did, thanks, but your email system needs to be fixed:
>>>>
>>>>
>>>> Do you mean Attestation failing part or something else?
>>>
>>> Yes:
>>>
>> I did not setup patatt in my workflow yet, which is why this is failing
>> attestation.
> 
> No, this is not for patatt (which would be good to have, I agree.)  This
> is due to Linaro, or you, not setting up DKIM properly.
> 
> As this works for other Linaro developers, you might want to ask them
> how they resolved it.
> 
some interestingly results.

I tried to validate DKIM using https://dkimvalidator.com which passes 
the validation.

Also checked my older patches mboxes which also passes DKIM.

Am not sure what went wrong with the previous patches.

Am hoping that the issue is fixed given that https://dkimvalidator.com 
seems to indicate that DKIM is passing, I will send v2 patches.


thanks,
Srini

> thanks,
> 
> greg k-h

On Tue, Aug 22, 2023 at 04:34:32PM +0200, Greg KH wrote:
> On Mon, Aug 14, 2023 at 05:52:30PM +0100, Srinivas Kandagatla wrote:
> > Here are some nvmem patches slightly more than usual for 6.6 that includes
> > 
> > - Support for NXP eFuse, qcom secure qfprom, QCM2290 nvmem providers
> > - core level cleanup around error handling and layout creation.
> > - few minor cleanups across providers drivers to use better
> >   apis and a typo fix.
> > 
> > Can you please queue them up for 6.6.
> 
> I did, thanks, but your email system needs to be fixed:

Oops, no, I've dropped them as I get the following build warning which
turns into an error, and you can't break the build.  How did you test
these?

drivers/nvmem/sec-qfprom.c: In function ‘sec_qfprom_probe’:
drivers/nvmem/sec-qfprom.c:59:13: error: unused variable ‘ret’ [-Werror=unused-variable]
   59 |         int ret;
      |             ^~~
cc1: all warnings being treated as errors

On 22/08/2023 15:35, Greg KH wrote:
> On Tue, Aug 22, 2023 at 04:34:32PM +0200, Greg KH wrote:
>> On Mon, Aug 14, 2023 at 05:52:30PM +0100, Srinivas Kandagatla wrote:
>>> Here are some nvmem patches slightly more than usual for 6.6 that includes
>>>
>>> - Support for NXP eFuse, qcom secure qfprom, QCM2290 nvmem providers
>>> - core level cleanup around error handling and layout creation.
>>> - few minor cleanups across providers drivers to use better
>>>    apis and a typo fix.
>>>
>>> Can you please queue them up for 6.6.
>>
>> I did, thanks, but your email system needs to be fixed:
> 
> Oops, no, I've dropped them as I get the following build warning which
> turns into an error, and you can't break the build.  How did you test
> these?
> 
> drivers/nvmem/sec-qfprom.c: In function ‘sec_qfprom_probe’:
> drivers/nvmem/sec-qfprom.c:59:13: error: unused variable ‘ret’ [-Werror=unused-variable]
>     59 |         int ret;
>        |             ^~~
> cc1: all warnings being treated as errors

Sorry, my bad, There is already a fix for this [1] which I forgot to push.


Let me send a v2 wrapping that fix into the original patch.

--srini

[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/srini/nvmem.git/commit/?h=for-next