public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Brian Norris <computersforpeace@gmail•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: linux-next: build failure after merge of the l2-mtd tree
Date: Mon, 21 Dec 2015 16:47:48 +1100	[thread overview]
Message-ID: <20151221164748.29442950@canb.auug.org.au> (raw)

Hi Brian,

After merging the l2-mtd tree, today's linux-next build (powerpc
ppc44x_defconfig) failed like this:

drivers/mtd/nand/ndfc.c: In function 'ndfc_chip_init':
drivers/mtd/nand/ndfc.c:177:2: error: 'ppdata' undeclared (first use in this function)
  ppdata.of_node = flash_np;
  ^

Caused by commit

  a61ae81a1907 ("mtd: nand: drop unnecessary partition parser data")

I applied this fix patch for today:

From: Stephen Rothwell <sfr@canb•auug.org.au>
Date: Mon, 21 Dec 2015 16:44:57 +1100
Subject: [PATCH] mtd: nand: fix for drop unnecessary partition parser data

Signed-off-by: Stephen Rothwell <sfr@canb•auug.org.au>
---
 drivers/mtd/nand/ndfc.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/mtd/nand/ndfc.c b/drivers/mtd/nand/ndfc.c
index 0709ea9dd8ed..7d72f4fe06a1 100644
--- a/drivers/mtd/nand/ndfc.c
+++ b/drivers/mtd/nand/ndfc.c
@@ -174,7 +174,6 @@ static int ndfc_chip_init(struct ndfc_controller *ndfc,
 		return -ENODEV;
 	nand_set_flash_node(chip, flash_np);
 
-	ppdata.of_node = flash_np;
 	mtd->name = kasprintf(GFP_KERNEL, "%s.%s", dev_name(&ndfc->ofdev->dev),
 			      flash_np->name);
 	if (!mtd->name) {
-- 
2.6.2

-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au

             reply	other threads:[~2015-12-21  5:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-21  5:47 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-08-28  2:19 linux-next: build failure after merge of the l2-mtd tree Stephen Rothwell
2017-08-28 22:06 ` Brian Norris
2017-02-09  1:08 Stephen Rothwell
2017-02-09  1:59 ` Brian Norris
2016-07-19  0:59 Stephen Rothwell
2016-07-19  1:20 ` Brian Norris
2016-07-19  1:46   ` Stephen Rothwell
2015-09-30  5:16 Stephen Rothwell
2014-05-22  5:30 Stephen Rothwell
2014-05-26 17:42 ` Brian Norris
2014-05-26 23:59   ` Stephen Rothwell
2014-05-27 10:40     ` Artem Bityutskiy
2014-05-27 22:49       ` Stephen Rothwell
2012-10-12  0:14 Stephen Rothwell
2012-10-12  4:51 ` Dinh Nguyen
2012-10-18  0:28 ` Stephen Rothwell
2012-10-18  9:26   ` Artem Bityutskiy
2012-02-07  2:58 Stephen Rothwell
2012-02-07  8:02 ` Artem Bityutskiy
2012-02-06  1:07 Stephen Rothwell
2012-02-06  9:14 ` Artem Bityutskiy
2012-02-06 21:10   ` Stephen Rothwell

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=20151221164748.29442950@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=computersforpeace@gmail$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    /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