* linux-next: build failure after merge of the nvmem tree
@ 2022-11-01 3:21 Stephen Rothwell
2022-11-01 7:27 ` Srinivas Kandagatla
0 siblings, 1 reply; 10+ messages in thread
From: Stephen Rothwell @ 2022-11-01 3:21 UTC (permalink / raw)
To: Srinivas Kandagatla
Cc: Patrick Delaunay, Linux Kernel Mailing List, Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 1490 bytes --]
Hi all,
After merging the nvmem tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/nvmem/nvmem_stm32_romem: struct of_device_id is 200 bytes. The last of 3 is:
0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x73 0x74 0x2c 0x73 0x74 0x6d 0x33 0x32 0x6d 0x70 0x31 0x33 0x2d 0x62 0x73 0x65 0x63 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
FATAL: modpost: drivers/nvmem/nvmem_stm32_romem: struct of_device_id is not terminated with a NULL entry!
Caused by commit
55ca3192d007 ("nvmem: stm32: add OP-TEE support for STM32MP13x")
I have used the nvmem tree from next-20221031 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: linux-next: build failure after merge of the nvmem tree
2022-11-01 3:21 linux-next: build failure after merge of the nvmem tree Stephen Rothwell
@ 2022-11-01 7:27 ` Srinivas Kandagatla
0 siblings, 0 replies; 10+ messages in thread
From: Srinivas Kandagatla @ 2022-11-01 7:27 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Patrick Delaunay, Linux Kernel Mailing List, Linux Next Mailing List
Thanks Stephen,
On 01/11/2022 03:21, Stephen Rothwell wrote:
> Hi all,
>
> After merging the nvmem tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/nvmem/nvmem_stm32_romem: struct of_device_id is 200 bytes. The last of 3 is:
> 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x73 0x74 0x2c 0x73 0x74 0x6d 0x33 0x32 0x6d 0x70 0x31 0x33 0x2d 0x62 0x73 0x65 0x63 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> FATAL: modpost: drivers/nvmem/nvmem_stm32_romem: struct of_device_id is not terminated with a NULL entry!
>
> Caused by commit
As there are some other comments on the patch, removing this until those
are fixed.
--srini
>
> 55ca3192d007 ("nvmem: stm32: add OP-TEE support for STM32MP13x")
>
> I have used the nvmem tree from next-20221031 for today.
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: linux-next: build failure after merge of the nvmem tree
2023-12-11 11:10 ` Srinivas Kandagatla
@ 2023-12-11 13:53 ` Miquel Raynal
0 siblings, 0 replies; 10+ messages in thread
From: Miquel Raynal @ 2023-12-11 13:53 UTC (permalink / raw)
To: Srinivas Kandagatla
Cc: Stephen Rothwell, Linux Kernel Mailing List, Linux Next Mailing List
Hi Srinivas,
srinivas.kandagatla@linaro.org wrote on Mon, 11 Dec 2023 11:10:19 +0000:
> Hi Miquel,
>
> On 11/12/2023 10:30, Miquel Raynal wrote:
> > Hi Srinivas,
> >
> > srinivas.kandagatla@linaro.org wrote on Mon, 11 Dec 2023 10:23:40 +0000:
> >
> >> Thankyou Stephen for the patch.
> >>
> >> On 11/12/2023 05:49, Stephen Rothwell wrote:
> >>> Hi all,
> >>>
> >>> After merging the nvmem tree, today's linux-next build (i386 defconfig)
> >>> failed like this:
> >>>
> >>> /home/sfr/next/next/drivers/nvmem/core.c: In function 'nvmem_cell_put':
> >>> /home/sfr/next/next/drivers/nvmem/core.c:1603:9: error: implicit declaration of function 'nvmem_layout_module_put' [-Werror=implicit-function-declaration]
> >>> 1603 | nvmem_layout_module_put(nvmem);
> >>> | ^~~~~~~~~~~~~~~~~~~~~~~
> >>>
> >>> Caused by commit
> >>>
> >>> ed7778e43271 ("nvmem: core: Rework layouts to become regular devices")
> >>>
> >>> I have applied the following patch for today.
> >>>
> >>> From: Stephen Rothwell <sfr@canb.auug.org.au>
> >>> Date: Mon, 11 Dec 2023 16:34:34 +1100
> >>> Subject: [PATCH] fix up for "nvmem: core: Rework layouts to become regular devices"
> >>>
> >>> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> >>> ---
> >>> drivers/nvmem/core.c | 5 +++++
> >>> 1 file changed, 5 insertions(+)
> >>>
> >>> diff --git a/drivers/nvmem/core.c b/drivers/nvmem/core.c
> >>> index 9fc452e8ada8..784b61eb4d8e 100644
> >>> --- a/drivers/nvmem/core.c
> >>> +++ b/drivers/nvmem/core.c
> >>> @@ -1491,6 +1491,11 @@ struct nvmem_cell *of_nvmem_cell_get(struct device_node *np, const char *id)
> >>> return cell;
> >>> }
> >>> EXPORT_SYMBOL_GPL(of_nvmem_cell_get);
> >>> +
> >>> +#else /* IS_ENABLED(CONFIG_OF) */
> >>> +
> >>> +static inline void nvmem_layout_module_put(struct nvmem_device *nvmem) { }
> >>> +
> >>
> >> I see no reason why nvmem_layout_module_put() should be even under IS_ENABLED(CONFIG_OF).
> >>
> >> Updated the patch with this fixed.
> >
> > Ok, works for me. I will send a fixup with the doc change (see the
> > other kernel test robot report) so you can squash it as well with the
> > original patch.
> >
> if you have fix up ready, can you send it.
Actually I mixed up two e-mails, I think this is all what is needed on
your branch. I don't have anything else. I thought there was a kernel
doc warning but I cannot find it anymore, so I believe I read my
e-mail too quickly.
Thanks,
Miquèl
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: linux-next: build failure after merge of the nvmem tree
2023-12-11 10:30 ` Miquel Raynal
@ 2023-12-11 11:10 ` Srinivas Kandagatla
2023-12-11 13:53 ` Miquel Raynal
0 siblings, 1 reply; 10+ messages in thread
From: Srinivas Kandagatla @ 2023-12-11 11:10 UTC (permalink / raw)
To: Miquel Raynal
Cc: Stephen Rothwell, Linux Kernel Mailing List, Linux Next Mailing List
Hi Miquel,
On 11/12/2023 10:30, Miquel Raynal wrote:
> Hi Srinivas,
>
> srinivas.kandagatla@linaro.org wrote on Mon, 11 Dec 2023 10:23:40 +0000:
>
>> Thankyou Stephen for the patch.
>>
>> On 11/12/2023 05:49, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> After merging the nvmem tree, today's linux-next build (i386 defconfig)
>>> failed like this:
>>>
>>> /home/sfr/next/next/drivers/nvmem/core.c: In function 'nvmem_cell_put':
>>> /home/sfr/next/next/drivers/nvmem/core.c:1603:9: error: implicit declaration of function 'nvmem_layout_module_put' [-Werror=implicit-function-declaration]
>>> 1603 | nvmem_layout_module_put(nvmem);
>>> | ^~~~~~~~~~~~~~~~~~~~~~~
>>>
>>> Caused by commit
>>>
>>> ed7778e43271 ("nvmem: core: Rework layouts to become regular devices")
>>>
>>> I have applied the following patch for today.
>>>
>>> From: Stephen Rothwell <sfr@canb.auug.org.au>
>>> Date: Mon, 11 Dec 2023 16:34:34 +1100
>>> Subject: [PATCH] fix up for "nvmem: core: Rework layouts to become regular devices"
>>>
>>> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
>>> ---
>>> drivers/nvmem/core.c | 5 +++++
>>> 1 file changed, 5 insertions(+)
>>>
>>> diff --git a/drivers/nvmem/core.c b/drivers/nvmem/core.c
>>> index 9fc452e8ada8..784b61eb4d8e 100644
>>> --- a/drivers/nvmem/core.c
>>> +++ b/drivers/nvmem/core.c
>>> @@ -1491,6 +1491,11 @@ struct nvmem_cell *of_nvmem_cell_get(struct device_node *np, const char *id)
>>> return cell;
>>> }
>>> EXPORT_SYMBOL_GPL(of_nvmem_cell_get);
>>> +
>>> +#else /* IS_ENABLED(CONFIG_OF) */
>>> +
>>> +static inline void nvmem_layout_module_put(struct nvmem_device *nvmem) { }
>>> +
>>
>> I see no reason why nvmem_layout_module_put() should be even under IS_ENABLED(CONFIG_OF).
>>
>> Updated the patch with this fixed.
>
> Ok, works for me. I will send a fixup with the doc change (see the
> other kernel test robot report) so you can squash it as well with the
> original patch.
>
if you have fix up ready, can you send it.
--srini
> I am surprised we get these now, I actually pushed the branch on my
> Github 0-day repository and got no negative report within 3 days.
> Anyway, I guess they have to prioritize the requests.
>
> Thanks,
> Miquèl
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: linux-next: build failure after merge of the nvmem tree
2023-12-11 10:23 ` Srinivas Kandagatla
@ 2023-12-11 10:30 ` Miquel Raynal
2023-12-11 11:10 ` Srinivas Kandagatla
0 siblings, 1 reply; 10+ messages in thread
From: Miquel Raynal @ 2023-12-11 10:30 UTC (permalink / raw)
To: Srinivas Kandagatla
Cc: Stephen Rothwell, Linux Kernel Mailing List, Linux Next Mailing List
Hi Srinivas,
srinivas.kandagatla@linaro.org wrote on Mon, 11 Dec 2023 10:23:40 +0000:
> Thankyou Stephen for the patch.
>
> On 11/12/2023 05:49, Stephen Rothwell wrote:
> > Hi all,
> >
> > After merging the nvmem tree, today's linux-next build (i386 defconfig)
> > failed like this:
> >
> > /home/sfr/next/next/drivers/nvmem/core.c: In function 'nvmem_cell_put':
> > /home/sfr/next/next/drivers/nvmem/core.c:1603:9: error: implicit declaration of function 'nvmem_layout_module_put' [-Werror=implicit-function-declaration]
> > 1603 | nvmem_layout_module_put(nvmem);
> > | ^~~~~~~~~~~~~~~~~~~~~~~
> >
> > Caused by commit
> >
> > ed7778e43271 ("nvmem: core: Rework layouts to become regular devices")
> >
> > I have applied the following patch for today.
> >
> > From: Stephen Rothwell <sfr@canb.auug.org.au>
> > Date: Mon, 11 Dec 2023 16:34:34 +1100
> > Subject: [PATCH] fix up for "nvmem: core: Rework layouts to become regular devices"
> >
> > Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> > ---
> > drivers/nvmem/core.c | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/drivers/nvmem/core.c b/drivers/nvmem/core.c
> > index 9fc452e8ada8..784b61eb4d8e 100644
> > --- a/drivers/nvmem/core.c
> > +++ b/drivers/nvmem/core.c
> > @@ -1491,6 +1491,11 @@ struct nvmem_cell *of_nvmem_cell_get(struct device_node *np, const char *id)
> > return cell;
> > }
> > EXPORT_SYMBOL_GPL(of_nvmem_cell_get);
> > +
> > +#else /* IS_ENABLED(CONFIG_OF) */
> > +
> > +static inline void nvmem_layout_module_put(struct nvmem_device *nvmem) { }
> > +
>
> I see no reason why nvmem_layout_module_put() should be even under IS_ENABLED(CONFIG_OF).
>
> Updated the patch with this fixed.
Ok, works for me. I will send a fixup with the doc change (see the
other kernel test robot report) so you can squash it as well with the
original patch.
I am surprised we get these now, I actually pushed the branch on my
Github 0-day repository and got no negative report within 3 days.
Anyway, I guess they have to prioritize the requests.
Thanks,
Miquèl
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: linux-next: build failure after merge of the nvmem tree
2023-12-11 5:49 Stephen Rothwell
@ 2023-12-11 10:23 ` Srinivas Kandagatla
2023-12-11 10:30 ` Miquel Raynal
0 siblings, 1 reply; 10+ messages in thread
From: Srinivas Kandagatla @ 2023-12-11 10:23 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Miquel Raynal, Linux Kernel Mailing List, Linux Next Mailing List
Thankyou Stephen for the patch.
On 11/12/2023 05:49, Stephen Rothwell wrote:
> Hi all,
>
> After merging the nvmem tree, today's linux-next build (i386 defconfig)
> failed like this:
>
> /home/sfr/next/next/drivers/nvmem/core.c: In function 'nvmem_cell_put':
> /home/sfr/next/next/drivers/nvmem/core.c:1603:9: error: implicit declaration of function 'nvmem_layout_module_put' [-Werror=implicit-function-declaration]
> 1603 | nvmem_layout_module_put(nvmem);
> | ^~~~~~~~~~~~~~~~~~~~~~~
>
> Caused by commit
>
> ed7778e43271 ("nvmem: core: Rework layouts to become regular devices")
>
> I have applied the following patch for today.
>
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Mon, 11 Dec 2023 16:34:34 +1100
> Subject: [PATCH] fix up for "nvmem: core: Rework layouts to become regular devices"
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
> drivers/nvmem/core.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/nvmem/core.c b/drivers/nvmem/core.c
> index 9fc452e8ada8..784b61eb4d8e 100644
> --- a/drivers/nvmem/core.c
> +++ b/drivers/nvmem/core.c
> @@ -1491,6 +1491,11 @@ struct nvmem_cell *of_nvmem_cell_get(struct device_node *np, const char *id)
> return cell;
> }
> EXPORT_SYMBOL_GPL(of_nvmem_cell_get);
> +
> +#else /* IS_ENABLED(CONFIG_OF) */
> +
> +static inline void nvmem_layout_module_put(struct nvmem_device *nvmem) { }
> +
I see no reason why nvmem_layout_module_put() should be even under
IS_ENABLED(CONFIG_OF).
Updated the patch with this fixed.
--srini
> #endif
>
> /**
^ permalink raw reply [flat|nested] 10+ messages in thread
* linux-next: build failure after merge of the nvmem tree
@ 2023-12-11 5:49 Stephen Rothwell
2023-12-11 10:23 ` Srinivas Kandagatla
0 siblings, 1 reply; 10+ messages in thread
From: Stephen Rothwell @ 2023-12-11 5:49 UTC (permalink / raw)
To: Srinivas Kandagatla
Cc: Miquel Raynal, Linux Kernel Mailing List, Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 1377 bytes --]
Hi all,
After merging the nvmem tree, today's linux-next build (i386 defconfig)
failed like this:
/home/sfr/next/next/drivers/nvmem/core.c: In function 'nvmem_cell_put':
/home/sfr/next/next/drivers/nvmem/core.c:1603:9: error: implicit declaration of function 'nvmem_layout_module_put' [-Werror=implicit-function-declaration]
1603 | nvmem_layout_module_put(nvmem);
| ^~~~~~~~~~~~~~~~~~~~~~~
Caused by commit
ed7778e43271 ("nvmem: core: Rework layouts to become regular devices")
I have applied the following patch for today.
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Mon, 11 Dec 2023 16:34:34 +1100
Subject: [PATCH] fix up for "nvmem: core: Rework layouts to become regular devices"
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
drivers/nvmem/core.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/drivers/nvmem/core.c b/drivers/nvmem/core.c
index 9fc452e8ada8..784b61eb4d8e 100644
--- a/drivers/nvmem/core.c
+++ b/drivers/nvmem/core.c
@@ -1491,6 +1491,11 @@ struct nvmem_cell *of_nvmem_cell_get(struct device_node *np, const char *id)
return cell;
}
EXPORT_SYMBOL_GPL(of_nvmem_cell_get);
+
+#else /* IS_ENABLED(CONFIG_OF) */
+
+static inline void nvmem_layout_module_put(struct nvmem_device *nvmem) { }
+
#endif
/**
--
2.40.1
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply related [flat|nested] 10+ messages in thread
* Re: linux-next: build failure after merge of the nvmem tree
2023-08-20 23:48 ` Stephen Rothwell
@ 2023-08-21 5:27 ` Komal Bajaj
0 siblings, 0 replies; 10+ messages in thread
From: Komal Bajaj @ 2023-08-21 5:27 UTC (permalink / raw)
To: Stephen Rothwell, Srinivas Kandagatla
Cc: Linux Kernel Mailing List, Linux Next Mailing List
On 8/21/2023 5:18 AM, Stephen Rothwell wrote:
> Hi all,
>
> On Tue, 15 Aug 2023 20:25:08 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>> After merging the nvmem tree, today's linux-next build (x86_64
>> allmodconfig) failed like this:
>>
>> 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
>>
>> Caused by commit
>>
>> 9c7f2bce8a0e ("nvmem: sec-qfprom: Add Qualcomm secure QFPROM support")
>>
>> I have used the nvmem tree from next-20230809 for today.
> Ping?
>
Hi Stephen,
Had already submitted a change for this -
https://lore.kernel.org/all/20230816130057.28717-1-quic_kbajaj@quicinc.com/
Thanks
Komal
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: linux-next: build failure after merge of the nvmem tree
2023-08-15 10:25 Stephen Rothwell
@ 2023-08-20 23:48 ` Stephen Rothwell
2023-08-21 5:27 ` Komal Bajaj
0 siblings, 1 reply; 10+ messages in thread
From: Stephen Rothwell @ 2023-08-20 23:48 UTC (permalink / raw)
To: Srinivas Kandagatla
Cc: Komal Bajaj, Linux Kernel Mailing List, Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 669 bytes --]
Hi all,
On Tue, 15 Aug 2023 20:25:08 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> After merging the nvmem tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> 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
>
> Caused by commit
>
> 9c7f2bce8a0e ("nvmem: sec-qfprom: Add Qualcomm secure QFPROM support")
>
> I have used the nvmem tree from next-20230809 for today.
Ping?
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* linux-next: build failure after merge of the nvmem tree
@ 2023-08-15 10:25 Stephen Rothwell
2023-08-20 23:48 ` Stephen Rothwell
0 siblings, 1 reply; 10+ messages in thread
From: Stephen Rothwell @ 2023-08-15 10:25 UTC (permalink / raw)
To: Srinivas Kandagatla
Cc: Komal Bajaj, Linux Kernel Mailing List, Linux Next Mailing List
[-- Attachment #1: Type: text/plain, Size: 545 bytes --]
Hi all,
After merging the nvmem tree, today's linux-next build (x86_64
allmodconfig) failed like this:
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
Caused by commit
9c7f2bce8a0e ("nvmem: sec-qfprom: Add Qualcomm secure QFPROM support")
I have used the nvmem tree from next-20230809 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2023-12-11 13:53 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-11-01 3:21 linux-next: build failure after merge of the nvmem tree Stephen Rothwell
2022-11-01 7:27 ` Srinivas Kandagatla
2023-08-15 10:25 Stephen Rothwell
2023-08-20 23:48 ` Stephen Rothwell
2023-08-21 5:27 ` Komal Bajaj
2023-12-11 5:49 Stephen Rothwell
2023-12-11 10:23 ` Srinivas Kandagatla
2023-12-11 10:30 ` Miquel Raynal
2023-12-11 11:10 ` Srinivas Kandagatla
2023-12-11 13:53 ` Miquel Raynal
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).