linux-kernel - Re: [PATCH 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] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 23 Aug 2023 09:54:04 +0100
From:   Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/22] nvmem: patches for v6.6



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@...aro.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