From: rogerq@ti.com (Roger Quadros)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] mtd: nand: omap: Fix build with CONFIG_MTD_NAND_OMAP_BCH=m
Date: Wed, 1 Oct 2014 14:33:28 +0300 [thread overview]
Message-ID: <1412163210-12948-1-git-send-email-rogerq@ti.com> (raw)
Hi,
Patch 1 fixes build with OMAP nand driver as built-in and the BCH driver as a module.
Ezequiel, I took the liberty to address an issue with your original patch so this is v2.
Patch 2 fixes the help message for CONFIG_MTD_NAND_OMAP_BCH to avoid user confusion.
CONFIG_MTD_NAND_OMAP_BCH is optional but doesn't harm on legacy OMAP platforms not having
the ELM/BCH hardware.
--
cheers,
-roger
Ezequiel Garcia (1):
mtd: nand: Force omap_elm to be built as a module if omap2_nand is a
module
Roger Quadros (1):
mtd: nand: omap: Correct CONFIG_MTD_NAND_OMAP_BCH help message
drivers/mtd/nand/Kconfig | 7 +++++--
drivers/mtd/nand/Makefile | 2 +-
2 files changed, 6 insertions(+), 3 deletions(-)
--
1.8.3.2
next reply other threads:[~2014-10-01 11:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 11:33 Roger Quadros [this message]
2014-10-01 11:33 ` [PATCH v2 1/2] mtd: nand: Force omap_elm to be built as a module if omap2_nand is a module Roger Quadros
2014-10-01 11:33 ` [PATCH 2/2] mtd: nand: omap: Correct CONFIG_MTD_NAND_OMAP_BCH help message Roger Quadros
2014-10-07 6:44 ` [PATCH 0/2] mtd: nand: omap: Fix build with CONFIG_MTD_NAND_OMAP_BCH=m Brian Norris
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=1412163210-12948-1-git-send-email-rogerq@ti.com \
--to=rogerq@ti.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).