public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Boris Brezillon <boris.brezillon@collabora.com>,
	 Cheng Ming Lin <chengminglin@mxic.com.tw>,
	 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, 04 Mar 2025 11:57:45 +0100	[thread overview]
Message-ID: <878qpl2hcm.fsf@bootlin.com> (raw)
In-Reply-To: <20250304132821.57c8d996@canb.auug.org.au> (Stephen Rothwell's message of "Tue, 4 Mar 2025 13:28:21 +1100")

Hello Stephen,

Thanks for the report.

> After merging the nand tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> In file included from drivers/mtd/nand/spi/macronix.c:11:
> drivers/mtd/nand/spi/macronix.c:190:63: error: expected expression before ',' token
>   190 |                      SPINAND_CONT_READ(macronix_set_cont_read),
>       |                                                               ^

I fixed the commit and pushed -f to fix the build failure.

The fix I made is not super nice so I will send a follow-up patch to
improve the style as the mistake comes from another unrelated patch.

Thanks,
Miquèl

  reply	other threads:[~2025-03-04 10:57 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-04  2:28 linux-next: build failure after merge of the nand tree Stephen Rothwell
2025-03-04 10:57 ` Miquel Raynal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-16  2:20 Stephen Rothwell
2025-01-17  2:23 ` Stephen Rothwell
2025-01-17  8:25   ` Miquel Raynal
2025-01-06  1:48 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
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=878qpl2hcm.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=boris.brezillon@collabora.com \
    --cc=chengminglin@mxic.com.tw \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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