public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] ARM: defconfigs: add MTD_SPI_NOR (new dependency for M25P80)
Date: Tue, 29 Apr 2014 16:22:08 -0300	[thread overview]
Message-ID: <20140429192208.GA28668@arch.cereza> (raw)
In-Reply-To: <20140429190603.GB9418@norris-Latitude-E6410>

On Apr 29, Brian Norris wrote:
> Hi Stephen,
> 
> On Fri, Apr 25, 2014 at 10:39:37AM -0600, Stephen Warren wrote:
> > On 04/17/2014 01:21 AM, Brian Norris wrote:
> > > These defconfigs contain the CONFIG_M25P80 symbol, which is now
> > > dependent on the MTD_SPI_NOR symbol. Add CONFIG_MTD_SPI_NOR to the
> > > relevant defconfigs.
> > > 
> > > At the same time, drop the now-nonexistent CONFIG_MTD_CHAR symbol.
> > 
> > I hadn't realized that the problem this patch solves was already present
> > in the code, so this patch is simply catching up the defconfigs rather
> > than part of a series which changed the code to cause the problem.
> 
> Yes, this is "catching up the defconfigs." The SPI_NOR framework is new,
> and I didn't want to generate defconfig noise until a few things
> stabilized (particularly, its Kconfig symbol name).
> 
> > So, this needs to be applied ASAP.
> > 
> > I think this should be split it up so that each defconfig can go through
> > the tree that owns it to avoid conflicts. If you repost split up, I can
> > apply the tegra_defconfig change to the Tegra tree.
> 
> OK, I'll try to split it up. Is ARM unique in tracking defconfigs in
> separate trees? I assume MIPS, PowerPC, and Blackfin won't require the
> same splitting? I'd like to avoid 31 patches when <20 could suffice.
> 
> I'll also rebase on linux-next. I think there may be a few conflicts.
> 

FWIW, I can take care of the patch for mvebu. Just drop it from your set
and I'll prepare one for Jason.
-- 
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com

  reply	other threads:[~2014-04-29 19:22 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-17  7:21 [PATCH 0/5] defconfigs: add MTD_SPI_NOR (dependency for M25P80) Brian Norris
2014-04-17  7:21 ` [PATCH 1/5] ARM: defconfigs: add MTD_SPI_NOR (new dependency " Brian Norris
2014-04-17 11:08   ` Marek Vasut
2014-04-21  2:32   ` Huang Shijie
2014-04-25 16:39   ` Stephen Warren
2014-04-29 17:22     ` Ezequiel Garcia
2014-04-29 17:48       ` Jason Cooper
2014-04-29 18:28         ` Ezequiel Garcia
2014-04-29 18:55           ` Jason Cooper
2014-04-29 19:06     ` Brian Norris
2014-04-29 19:22       ` Ezequiel Garcia [this message]
2014-05-01  6:04         ` Brian Norris
2014-04-29 19:42       ` Stephen Warren
2014-05-01  6:07         ` Brian Norris
2014-05-01 16:48           ` Stephen Warren
2014-04-30  5:39       ` Huang Shijie
2014-04-30 11:45       ` Jason Cooper
2014-05-01  6:08         ` Brian Norris
2014-05-03 22:51         ` Olof Johansson
2014-05-04 17:42           ` Jason Cooper
2014-05-04 18:53             ` Olof Johansson
2014-05-06 17:05               ` Brian Norris
2014-04-17 10:53 ` [PATCH 0/5] defconfigs: add MTD_SPI_NOR (dependency " Thierry Reding
2014-04-18  6:30   ` Brian Norris
2014-04-21 14:52     ` Marek Vasut
2014-04-17 11:07 ` Marek Vasut

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=20140429192208.GA28668@arch.cereza \
    --to=ezequiel.garcia@free-electrons.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