public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: Olof Johansson <olof@lixom.net>
Cc: Marek Vasut <marex@denx.de>,
	Russell King <linux@arm.linux.org.uk>,
	Jason Cooper <jason@lakedaemon.net>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Thierry Reding <thierry.reding@gmail.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	Shawn Guo <shawn.guo@freescale.com>,
	Sascha Hauer <kernel@pengutronix.de>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/5] ARM: defconfigs: add MTD_SPI_NOR (new dependency for M25P80)
Date: Tue, 6 May 2014 10:05:26 -0700	[thread overview]
Message-ID: <20140506170526.GA28907@ld-irv-0074> (raw)
In-Reply-To: <CAOesGMh09AQ3Y-cdXFov3-+RZHDYTVw=MWngRumHc0hnB-CGOg@mail.gmail.com>

On Sun, May 04, 2014 at 11:53:22AM -0700, Olof Johansson wrote:
> On Sun, May 4, 2014 at 10:42 AM, Jason Cooper <jason@lakedaemon.net> wrote:
> > On Sat, May 03, 2014 at 03:51:11PM -0700, Olof Johansson wrote:
> >> Cases like these are easiest that we just take the patch directly in
> >> an early-merge branch (i.e. cleanup or fixes-non-critical, or a
> >> generic depends branch), and if there's conflicts as topics are merged
> >> in from subplatforms we can deal with it then.
> >
> > Are you referring to basing on -rc1, or the series being split up to
> > the individual sub-arch maintainers?
> >
> > *slightly* confused,
> 
> I'm referring to us taking the patch into something like our cleanup
> branch, and any branches that come in from you or other subplatforms
> will be merged on top, so we can resolve conflicts there and then.
> We'll merge in the cleanup branch into other next/* branches as needed
> to resolve the conflicts in our tree instead of percolating them all
> the way up.

In case you didn't notice, I already had split up the patch series a
little more for v2 (based on -rc1 still), and most of it seems to be
going through the sub-arch trees, I think. There is one patch targeted
directly at arm-soc (that's you, Olof?).

Let me know if v2 has any problems.

Thanks,
Brian

  reply	other threads:[~2014-05-06 17:05 UTC|newest]

Thread overview: 32+ 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
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 [this message]
2014-04-17  7:21 ` [PATCH 2/5] blackfin: " Brian Norris
2014-04-17  7:21 ` [PATCH 3/5] mips: " Brian Norris
2014-04-19  0:24   ` Florian Fainelli
2014-04-19  0:49     ` Brian Norris
2014-04-17  7:21 ` [PATCH 4/5] powerpc: " Brian Norris
2014-04-17  7:21 ` [PATCH 5/5] sh: defconfig: " 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=20140506170526.GA28907@ld-irv-0074 \
    --to=computersforpeace@gmail.com \
    --cc=jason@lakedaemon.net \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux@arm.linux.org.uk \
    --cc=marex@denx.de \
    --cc=olof@lixom.net \
    --cc=shawn.guo@freescale.com \
    --cc=swarren@wwwdotorg.org \
    --cc=thierry.reding@gmail.com \
    /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