From: Greg KH <gregkh@linuxfoundation.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/22] nvmem: patches for v6.6
Date: Tue, 22 Aug 2023 16:35:25 +0200 [thread overview]
Message-ID: <2023082251-browsing-moocher-6ecf@gregkh> (raw)
In-Reply-To: <2023082217-banter-craftwork-281a@gregkh>
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
next prev parent reply other threads:[~2023-08-22 14:35 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 16:52 [PATCH 00/22] nvmem: patches for v6.6 Srinivas Kandagatla
2023-08-14 16:52 ` [PATCH 01/22] dt-bindings: nvmem: fixed-cell: add compatible for MAC cells Srinivas Kandagatla
2023-08-14 16:52 ` [PATCH 02/22] nvmem: sunxi_sid: Convert to devm_platform_ioremap_resource() Srinivas Kandagatla
2023-08-14 16:52 ` [PATCH 03/22] nvmem: brcm_nvram: Use devm_platform_get_and_ioremap_resource() Srinivas Kandagatla
2023-08-14 16:52 ` [PATCH 04/22] nvmem: lpc18xx_otp: Convert to devm_platform_ioremap_resource() Srinivas Kandagatla
2023-08-14 16:52 ` [PATCH 05/22] nvmem: meson-mx-efuse: " Srinivas Kandagatla
2023-08-14 16:52 ` [PATCH 06/22] nvmem: rockchip-efuse: Use devm_platform_get_and_ioremap_resource() Srinivas Kandagatla
2023-08-14 16:52 ` [PATCH 07/22] nvmem: stm32-romem: " Srinivas Kandagatla
2023-08-14 16:52 ` [PATCH 08/22] nvmem: qfprom: do some cleanup Srinivas Kandagatla
2023-08-14 16:52 ` [PATCH 09/22] nvmem: uniphier: Use devm_platform_get_and_ioremap_resource() Srinivas Kandagatla
2023-08-14 16:52 ` [PATCH 10/22] dt-bindings: nvmem: qfprom: Add compatible for MSM8226 Srinivas Kandagatla
2023-08-14 16:52 ` [PATCH 11/22] dt-bindings: nvmem: Add t1023-sfp efuse support Srinivas Kandagatla
2023-08-14 16:52 ` [PATCH 12/22] nvmem: add new NXP QorIQ eFuse driver Srinivas Kandagatla
2023-08-14 16:52 ` [PATCH 13/22] nvmem: Explicitly include correct DT includes Srinivas Kandagatla
2023-08-14 16:52 ` [PATCH 14/22] nvmem: Kconfig: Fix typo "drive" -> "driver" Srinivas Kandagatla
2023-08-14 16:52 ` [PATCH 15/22] dt-bindings: nvmem: Add compatible for QCM2290 Srinivas Kandagatla
2023-08-14 16:52 ` [PATCH 16/22] dt-bindings: nvmem: sec-qfprom: Add bindings for secure qfprom Srinivas Kandagatla
2023-08-14 16:52 ` [PATCH 17/22] nvmem: sec-qfprom: Add Qualcomm secure QFPROM support Srinivas Kandagatla
2023-08-14 16:52 ` [PATCH 18/22] nvmem: u-boot-env:: Replace zero-length array with DECLARE_FLEX_ARRAY() helper Srinivas Kandagatla
2023-08-14 16:52 ` [PATCH 19/22] nvmem: core: Create all cells before adding the nvmem device Srinivas Kandagatla
2023-08-14 16:52 ` [PATCH 20/22] nvmem: core: Return NULL when no nvmem layout is found Srinivas Kandagatla
2023-08-14 16:52 ` [PATCH 21/22] nvmem: core: Do not open-code existing functions Srinivas Kandagatla
2023-08-14 16:52 ` [PATCH 22/22] nvmem: core: Notify when a new layout is registered Srinivas Kandagatla
2023-08-22 14:34 ` [PATCH 00/22] nvmem: patches for v6.6 Greg KH
2023-08-22 14:35 ` Greg KH [this message]
2023-08-22 14:50 ` Srinivas Kandagatla
2023-08-22 17:29 ` Srinivas Kandagatla
2023-08-22 17:37 ` Greg KH
2023-08-23 8:54 ` Srinivas Kandagatla
2023-08-23 8:59 ` Greg KH
2023-08-23 13:26 ` Srinivas Kandagatla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2023082251-browsing-moocher-6ecf@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.kandagatla@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox