From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Miquel Raynal <miquel.raynal@bootlin•com>,
Boris Brezillon <boris.brezillon@collabora•com>
Cc: Md Sadre Alam <quic_mdalam@quicinc•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build failure after merge of the nand tree
Date: Tue, 7 Jan 2025 12:46:40 +1100 [thread overview]
Message-ID: <20250107124640.2442512f@canb.auug.org.au> (raw)
In-Reply-To: <409116b0-ebb2-025f-ba8c-0eff3e7e11dc@quicinc.com>
[-- Attachment #1: Type: text/plain, Size: 2089 bytes --]
Hi all,
On Mon, 6 Jan 2025 18:53:01 +0530 Md Sadre Alam <quic_mdalam@quicinc•com> wrote:
>
> On 1/6/2025 7:21 AM, Stephen Rothwell wrote:
> >
> > On Mon, 6 Jan 2025 12:48:34 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> >>
> >> After merging the nand tree, today's linux-next build
> >> (x86_64_allmodconfig) failed like this:
> >>
> >> In file included from include/linux/string.h:389,
> >> from include/linux/bitmap.h:13,
> >> from include/linux/cpumask.h:12,
> >> from include/linux/smp.h:13,
> >> from include/linux/lockdep.h:14,
> >> from include/linux/mutex.h:17,
> >> from include/linux/notifier.h:14,
> >> from include/linux/clk.h:14,
> >> from drivers/mtd/nand/qpic_common.c:6:
> >> In function 'fortify_memset_chk',
> >> inlined from 'qcom_clear_bam_transaction' at drivers/mtd/nand/qpic_common.c:88:2:
> >> include/linux/fortify-string.h:480:25: error: call to '__write_overflow_field' declared with attribute warning: detected write beyond size of field (1st parameter); maybe use struct_group()? [-Werror=attribute-warning]
> >> 480 | __write_overflow_field(p_size_field, size);
> >> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >> cc1: all warnings being treated as errors
> >>
> >> Caused by commit
> >>
> >> fdf3ee5c6e52 ("mtd: nand: Add qpic_common API file")
> >
> > Actually caused by commit
> >
> > 8c52932da5e6 ("mtd: rawnand: qcom: cleanup qcom_nandc driver")
> I have posted the fix. Please check the patch at [1]
> [1] https://lore.kernel.org/lkml/20250106131558.2219136-1-quic_mdalam@quicinc.com/T/#u
I have applied that patch today instead of reverting the tree. I will
remove this patch when I see it (or some other fix) applied to the nand
tree.
When applying it, you could add
Tested-by: Stephen Rothwell <sfr@canb•auug.org.au> # build testing
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-01-07 1:46 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 1:48 linux-next: build failure after merge of the nand tree Stephen Rothwell
2025-01-06 1:51 ` Stephen Rothwell
2025-01-06 6:16 ` Md Sadre Alam
2025-01-06 13:23 ` Md Sadre Alam
2025-01-07 1:46 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-29 10:07 Thierry Reding
2026-04-29 17:47 ` Miquel Raynal
2025-03-04 2:28 Stephen Rothwell
2025-03-04 10:57 ` Miquel Raynal
2025-01-16 2:20 Stephen Rothwell
2025-01-17 2:23 ` Stephen Rothwell
2025-01-17 8:25 ` Miquel Raynal
2023-08-21 2:02 Stephen Rothwell
2023-08-21 5:44 ` Md Sadre Alam
2022-09-21 1:32 Stephen Rothwell
2020-12-08 2:14 Stephen Rothwell
2020-09-14 1:45 Stephen Rothwell
2020-09-14 9:50 ` Alex Dewar
2020-09-14 10:58 ` Miquel Raynal
2020-09-08 3:35 Stephen Rothwell
2020-09-10 4:12 ` Stephen Rothwell
2020-09-11 16:58 ` Miquel Raynal
2020-05-25 10:45 Stephen Rothwell
2020-05-25 11:54 ` Miquel Raynal
2020-05-12 4:08 Stephen Rothwell
2020-05-12 7:04 ` Miquel Raynal
2020-03-11 2:16 Stephen Rothwell
2020-03-11 10:10 ` Miquel Raynal
2020-03-11 14:01 ` Boris Brezillon
2020-03-11 19:20 ` Janusz Krzysztofik
2019-04-01 23:14 Stephen Rothwell
2019-04-01 23:31 ` Paul Cercueil
2019-04-02 7:27 ` Miquel Raynal
2019-04-02 9:21 ` Miquel Raynal
2019-04-02 11:56 ` Miquel Raynal
2019-04-02 12:00 ` Paul Cercueil
2019-04-02 12:16 ` Miquel Raynal
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=20250107124640.2442512f@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=boris.brezillon@collabora$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=miquel.raynal@bootlin$(echo .)com \
--cc=quic_mdalam@quicinc$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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