linux-kernel - Re: [PATCH v2 00/22] nvmem: patches for v6.6

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]

Message-ID: <7c3cd9b5-89cf-274f-a6e7-351ed2aaed2e@linaro.org>
Date:   Wed, 23 Aug 2023 15:47:35 +0100
From:   Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 00/22] nvmem: patches for v6.6



On 23/08/2023 15:35, Greg KH wrote:
> On Wed, Aug 23, 2023 at 02:27:22PM +0100, srinivas.kandagatla@...aro.org wrote:
>> From: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
>>
>> 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.
> 
> Better, but I don't have your gpg key, is it in the kernel keyring?

Its not in kernel keyring yet, I sent it out today morning for 
inclusion. But key should be some of the old keyservers though.

> 
> Grabbing thread from lore.kernel.org/all/20230823132744.350618-1-srinivas.kandagatla@...aro.org/t.mbox.gz
> Analyzing 23 messages in the thread
> Checking attestation on all messages, may take a moment...
> ---
>    ✗ [PATCH v2 1/22] dt-bindings: nvmem: fixed-cell: add compatible for MAC cells
>    ✗ [PATCH v2 2/22] nvmem: sunxi_sid: Convert to devm_platform_ioremap_resource()
>    ✗ [PATCH v2 3/22] nvmem: brcm_nvram: Use devm_platform_get_and_ioremap_resource()
>    ✗ [PATCH v2 4/22] nvmem: lpc18xx_otp: Convert to devm_platform_ioremap_resource()
>    ✗ [PATCH v2 5/22] nvmem: meson-mx-efuse: Convert to devm_platform_ioremap_resource()
>    ✗ [PATCH v2 6/22] nvmem: rockchip-efuse: Use devm_platform_get_and_ioremap_resource()
>    ✗ [PATCH v2 7/22] nvmem: stm32-romem: Use devm_platform_get_and_ioremap_resource()
>    ✗ [PATCH v2 8/22] nvmem: qfprom: do some cleanup
>    ✗ [PATCH v2 9/22] nvmem: uniphier: Use devm_platform_get_and_ioremap_resource()
>    ✗ [PATCH v2 10/22] dt-bindings: nvmem: qfprom: Add compatible for MSM8226
>    ✗ [PATCH v2 11/22] dt-bindings: nvmem: Add t1023-sfp efuse support
>    ✗ [PATCH v2 12/22] nvmem: add new NXP QorIQ eFuse driver
>    ✗ [PATCH v2 13/22] nvmem: Explicitly include correct DT includes
>    ✗ [PATCH v2 14/22] nvmem: Kconfig: Fix typo "drive" -> "driver"
>    ✗ [PATCH v2 15/22] dt-bindings: nvmem: Add compatible for QCM2290
>    ✗ [PATCH v2 16/22] dt-bindings: nvmem: sec-qfprom: Add bindings for secure qfprom
>    ✗ [PATCH v2 17/22] nvmem: sec-qfprom: Add Qualcomm secure QFPROM support
>    ✗ [PATCH v2 18/22] nvmem: u-boot-env:: Replace zero-length array with DECLARE_FLEX_ARRAY() helper
>    ✗ [PATCH v2 19/22] nvmem: core: Create all cells before adding the nvmem device
>    ✗ [PATCH v2 20/22] nvmem: core: Return NULL when no nvmem layout is found
>    ✗ [PATCH v2 21/22] nvmem: core: Do not open-code existing functions
>    ✗ [PATCH v2 22/22] nvmem: core: Notify when a new layout is registered
>    ---
>    ✗ BADSIG: openpgp/srinivas.kandagatla@...aro.org
>    ✓ Signed: DKIM/linaro.org
> 
> At least DKIM passes :)

> 
> Anyway, all now queued up, they pass my local build tests, thanks for
> fixing that up.

thanks for picking these up.

--srini
> 
> greg k-h