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] [day] [month] [year] [list]

Message-ID: <1abdb67b-6efd-474c-ef50-abd8cebe3803@linaro.org>
Date:   Wed, 23 Aug 2023 14:26:41 +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 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