From: Stephen Warren <swarren@wwwdotorg.org>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Marek Vasut <marex@denx.de>,
linux-mtd@lists.infradead.org,
Russell King <linux@arm.linux.org.uk>,
Shawn Guo <shawn.guo@freescale.com>,
Sascha Hauer <kernel@pengutronix.de>,
Thierry Reding <thierry.reding@gmail.com>,
Olof Johansson <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org,
"arm@kernel.org" <arm@kernel.org>
Subject: Re: [PATCH 1/5] ARM: defconfigs: add MTD_SPI_NOR (new dependency for M25P80)
Date: Thu, 01 May 2014 10:48:48 -0600 [thread overview]
Message-ID: <53627AF0.6060408@wwwdotorg.org> (raw)
In-Reply-To: <20140501060739.GH2497@norris-Latitude-E6410>
On 05/01/2014 12:07 AM, Brian Norris wrote:
> On Tue, Apr 29, 2014 at 01:42:50PM -0600, Stephen Warren wrote:
>> I guess you could also just see if arm-soc (arm@kernel.org) will take
>> this patch, and deal with any merge conflicts that arise when they merge
>> all the sub-arch defconfig changes. I CC'd them to find out if they
>> think that's a better idea.
>
> I'm preparing a split patch series and should send v2 shortly. A few of
> the unaccounted platforms + the multi-platform are lumped together for
> direct inclusion in arm-soc (?).
>
> What is this arm@kernel.org you speak of? My Google-fu doesn't turn up a
> separate arm-soc email / mailing list, and it's not in MAINTAINERS.
It's the email address of the ARM SoC maintainers (Arnd, Olof, Kevin).
All the ARM sub-architecture maintainers send their pull requests there,
which all get aggregated and forwarded to Linus. They also take some
patches directly, for cross-sub-architecture stuff like
multi_v7_defconfig, or small amounts of bug-fixes after the main pull
requests are sent.
next prev parent reply other threads:[~2014-05-01 16:48 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 " 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 [this message]
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 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=53627AF0.6060408@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=arm@kernel.org \
--cc=computersforpeace@gmail.com \
--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=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
Powered by JetHome