All of lore.kernel.org
 help / color / mirror / Atom feed
From: Md Sadre Alam <quic_mdalam@quicinc.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Boris Brezillon <boris.brezillon@collabora.com>
Cc: Sricharan Ramabadhran <quic_srichara@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: Mon, 21 Aug 2023 11:14:55 +0530	[thread overview]
Message-ID: <78220b51-da70-c2d6-3aaa-20c17251b021@quicinc.com> (raw)
In-Reply-To: <20230821120213.403fcefe@canb.auug.org.au>



On 8/21/2023 7:32 AM, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the nand tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> drivers/mtd/nand/raw/qcom_nandc.c: In function 'qcom_parse_instructions':
> drivers/mtd/nand/raw/qcom_nandc.c:2596:38: error: unused variable 'nandc' [-Werror=unused-variable]
>   2596 |         struct qcom_nand_controller *nandc = get_qcom_nand_controller(chip);
>        |                                      ^~~~~
> cc1: all warnings being treated as errors
> 
> Caused by commit
> 
>    5a7688a3e2e6 ("mtd: rawnand: qcom: Add read/read_start ops in exec_op path")
> 
> I have used the nand tree from next-20230818 for today.

   I have posted a patch to fix this build issue.

   Link: https://patchwork.kernel.org/project/linux-arm-msm/patch/20230821053513.13728-1-quic_mdalam@quicinc.com/

> 

  reply	other threads:[~2023-08-21  5:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-21  2:02 linux-next: build failure after merge of the nand tree Stephen Rothwell
2023-08-21  5:44 ` Md Sadre Alam [this message]
  -- strict thread matches above, loose matches on Subject: below --
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=78220b51-da70-c2d6-3aaa-20c17251b021@quicinc.com \
    --to=quic_mdalam@quicinc.com \
    --cc=boris.brezillon@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=quic_srichara@quicinc.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.