All of lore.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@bootlin.com>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the nand tree
Date: Mon, 8 Oct 2018 09:53:34 +0200	[thread overview]
Message-ID: <20181008095334.6850f033@xps13> (raw)
In-Reply-To: <20181008113842.4bfc8cf9@canb.auug.org.au>

Hi Stephen,

Stephen Rothwell <sfr@canb.auug.org.au> wrote on Mon, 8 Oct 2018
11:38:42 +1100:

> Hi Boris,

Boris is still there but I'm in charge of the NAND tree these days (and
the one to blame too for this one :) ).

> 
> After merging the nand tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
> 
> drivers/mtd/nand/raw/nand_toshiba.c: In function 'toshiba_nand_read_page_benand':
> drivers/mtd/nand/raw/nand_toshiba.c:54:19: warning: unused variable 'mtd' [-Wunused-variable]
>   struct mtd_info *mtd = nand_to_mtd(chip);
>                    ^~~
> drivers/mtd/nand/raw/nand_toshiba.c: In function 'toshiba_nand_read_subpage_benand':
> drivers/mtd/nand/raw/nand_toshiba.c:68:19: warning: unused variable 'mtd' [-Wunused-variable]
>   struct mtd_info *mtd = nand_to_mtd(chip);
>                    ^~~
> 
> Introduced by commit
> 
>   fe8b76ec9886 ("mtd: rawnand: toshiba: Pass a single nand_chip object to the status helper")

Thanks for the warning, I'll correct it for tomorrow.

Kind regards,
Miquèl

  reply	other threads:[~2018-10-08  7:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-08  0:38 linux-next: build warning after merge of the nand tree Stephen Rothwell
2018-10-08  7:53 ` Miquel Raynal [this message]
2018-10-08 11:06   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2023-12-01  1:56 Stephen Rothwell
2023-12-01  5:03 ` David Regan
2023-12-01 11:55   ` Miquel Raynal
2023-01-16  3:32 Stephen Rothwell
2022-02-08  6:00 Stephen Rothwell
2020-11-20  0:39 Stephen Rothwell
2020-11-20 11:23 ` Miquel Raynal
2020-11-20 12:01   ` Boris Brezillon
2020-11-20 12:58     ` Serge Semin
2020-11-20 13:01     ` Serge Semin
2020-11-03  6:37 Stephen Rothwell
2020-11-06  4:31 ` Stephen Rothwell
2020-09-14  1:40 Stephen Rothwell
2020-03-11  2:06 Stephen Rothwell
2019-04-02 23:22 Stephen Rothwell
2019-04-03  7:49 ` Miquel Raynal
2018-07-19  2:28 Stephen Rothwell
2018-07-09  1:51 Stephen Rothwell
2018-07-09  6:16 ` Boris Brezillon
2018-07-09  6:51   ` 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=20181008095334.6850f033@xps13 \
    --to=miquel.raynal@bootlin.com \
    --cc=boris.brezillon@bootlin.com \
    --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 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.