mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Alexander Shiyan <shc_work@mail.ru>
To: barebox@lists.infradead.org
Subject: [PATCH 7/8] Remove bad Kconfig reference to MTD_NAND
Date: Sat,  8 Dec 2012 10:51:25 +0400	[thread overview]
Message-ID: <1354949486-12917-7-git-send-email-shc_work@mail.ru> (raw)
In-Reply-To: <1354949486-12917-1-git-send-email-shc_work@mail.ru>

Barebox not contain symbol MTD_NAND, so remove all references to it.

Signed-off-by: Alexander Shiyan <shc_work@mail.ru>
---
 drivers/mtd/nand/Kconfig |    1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/drivers/mtd/nand/Kconfig b/drivers/mtd/nand/Kconfig
index aa3ea34..49daabf 100644
--- a/drivers/mtd/nand/Kconfig
+++ b/drivers/mtd/nand/Kconfig
@@ -104,7 +104,6 @@ config MTD_NAND_ECC_SMC
 
 config MTD_NAND_MUSEUM_IDS
 	bool "Enable chip ids for obsolete ancient NAND devices"
-	depends on MTD_NAND
 	default n
 	help
 	  Enable this option only when your board has first generation
-- 
1.7.8.6


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2012-12-08  6:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-08  6:51 [PATCH 1/8] Cleanup Kconfig files Alexander Shiyan
2012-12-08  6:51 ` [PATCH 2/8] Remove bad Kconfig reference to HAS_CFI Alexander Shiyan
2012-12-08  6:51 ` [PATCH 3/8] Remove bad Kconfig reference to HAVE_MMU Alexander Shiyan
2012-12-08  6:51 ` [PATCH 4/8] Remove bad Kconfig reference to HAVE_CLK Alexander Shiyan
2012-12-08  6:51 ` [PATCH 5/8] Remove bad Kconfig reference to DISK_DRIVE Alexander Shiyan
2012-12-08  6:51 ` [PATCH 6/8] Remove bad Kconfig reference to HAS_PCI Alexander Shiyan
2012-12-08  6:51 ` Alexander Shiyan [this message]
2012-12-08  6:51 ` [PATCH 8/8] Fix wrong Kconfig reference to ARCH_IMX31 Alexander Shiyan
2012-12-08 14:26 ` [PATCH 1/8] Cleanup Kconfig files Sascha Hauer

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=1354949486-12917-7-git-send-email-shc_work@mail.ru \
    --to=shc_work@mail.ru \
    --cc=barebox@lists.infradead.org \
    /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