From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Brian Norris <computersforpeace@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Huang Shijie <b32955@freescale.com>, Marek Vasut <marex@denx.de>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 03/12] ARM: keystone: add MTD_SPI_NOR (new dependency for M25P80)
Date: Thu, 1 May 2014 10:16:05 -0400 [thread overview]
Message-ID: <53625725.6060401@ti.com> (raw)
In-Reply-To: <1398925607-7482-4-git-send-email-computersforpeace@gmail.com>
On Thursday 01 May 2014 02:26 AM, Brian Norris wrote:
> This defconfig contains the CONFIG_M25P80 symbol, which is now
> dependent on the MTD_SPI_NOR symbol. Add CONFIG_MTD_SPI_NOR to satisfy
> the new dependency.
>
> Signed-off-by: Brian Norris <computersforpeace@gmail.com>
> Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: linux-kernel@vger.kernel.org
> ---
I will pick this up for 3.16.
> arch/arm/configs/keystone_defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/configs/keystone_defconfig b/arch/arm/configs/keystone_defconfig
> index ec9a41d50680..b3057730689f 100644
> --- a/arch/arm/configs/keystone_defconfig
> +++ b/arch/arm/configs/keystone_defconfig
> @@ -112,6 +112,7 @@ CONFIG_MTD_PLATRAM=y
> CONFIG_MTD_M25P80=y
> CONFIG_MTD_NAND=y
> CONFIG_MTD_NAND_DAVINCI=y
> +CONFIG_MTD_SPI_NOR=y
> CONFIG_MTD_UBI=y
> CONFIG_PROC_DEVICETREE=y
> CONFIG_BLK_DEV_LOOP=y
>
next prev parent reply other threads:[~2014-05-01 14:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1398925607-7482-1-git-send-email-computersforpeace@gmail.com>
2014-05-01 6:26 ` [PATCH v2 01/12] ARM: imx/mxs defconfigs: add MTD_SPI_NOR (new dependency for M25P80) Brian Norris
2014-05-01 6:43 ` Paul Bolle
2014-05-06 13:55 ` Shawn Guo
2014-05-01 6:26 ` [PATCH v2 02/12] ARM: " Brian Norris
2014-05-01 8:54 ` Simon Horman
2014-05-06 18:12 ` Brian Norris
2014-05-11 0:43 ` Simon Horman
2014-05-01 6:26 ` [PATCH v2 03/12] ARM: keystone: " Brian Norris
2014-05-01 14:16 ` Santosh Shilimkar [this message]
2014-05-01 6:26 ` [PATCH v2 04/12] ARM: tegra: " Brian Norris
2014-05-01 17:26 ` Stephen Warren
2014-05-01 6:26 ` [PATCH v2 05/12] ARM: lpc32xx: " Brian Norris
2014-05-01 17:21 ` Roland Stigge
2014-05-06 17:15 ` Brian Norris
2014-05-01 6:26 ` [PATCH v2 06/12] ARM: at91: " Brian Norris
2014-09-02 8:36 ` Nicolas Ferre
2014-05-01 6:26 ` [PATCH v2 07/12] ARM: shmobile: " Brian Norris
2014-05-01 6:26 ` [PATCH v2 08/12] ARM: marvell: " Brian Norris
2014-05-01 17:53 ` Ezequiel Garcia
2014-05-05 1:03 ` Jason Cooper
2014-05-01 6:26 ` [PATCH v2 09/12] blackfin: defconfigs: " Brian Norris
2014-06-12 9:00 ` Steven Miao
2014-05-01 6:26 ` [PATCH v2 10/12] mips: " Brian Norris
2014-05-01 6:26 ` [PATCH v2 11/12] powerpc: " Brian Norris
2014-05-01 6:26 ` [PATCH v2 12/12] sh: defconfig: " 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=53625725.6060401@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=b32955@freescale.com \
--cc=computersforpeace@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marex@denx.de \
/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).