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]
Message-ID: <c4275bc0-a608-ffe6-906a-f79037b19191@linaro.org>
Date:   Tue, 22 Aug 2023 15:50:32 +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 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


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ