From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2] ARM: Push selects for TWD/SCU into machine entries
Date: Thu, 25 Oct 2012 11:04:41 -0700 [thread overview]
Message-ID: <50897F39.9030702@codeaurora.org> (raw)
In-Reply-To: <50882B6E.5020103@wwwdotorg.org>
On 10/24/12 10:54, Stephen Warren wrote:
> Where will this patch be merged?
>
> It probably won't happen for 3.8, but that config fragment will move to
> arch/arm/mach-tegra/Kconfig when Tegra enables single zImage support, I
> believe. So, it'd be good to make sure this patch gets merged somewhere
> that could be used as a baseline for other arm-soc branches if needed,
> to avoid merge conflicts.
I was hoping this could go through the arm-soc tree for the 3.8 merge
window.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@codeaurora.org>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, David Brown <davidb@codeaurora.org>,
Kukjin Kim <kgene.kim@samsung.com>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <rob.herring@calxeda.com>,
Russell King <linux@arm.linux.org.uk>,
Sascha Hauer <kernel@pengutronix.de>,
Shiraz Hashim <shiraz.hashim@st.com>,
Srinidhi Kasagar <srinidhi.kasagar@stericsson.com>,
Tony Lindgren <tony@atomide.com>,
"arm@kernel.org" <arm@kernel.org>
Subject: Re: [PATCHv2] ARM: Push selects for TWD/SCU into machine entries
Date: Thu, 25 Oct 2012 11:04:41 -0700 [thread overview]
Message-ID: <50897F39.9030702@codeaurora.org> (raw)
In-Reply-To: <50882B6E.5020103@wwwdotorg.org>
On 10/24/12 10:54, Stephen Warren wrote:
> Where will this patch be merged?
>
> It probably won't happen for 3.8, but that config fragment will move to
> arch/arm/mach-tegra/Kconfig when Tegra enables single zImage support, I
> believe. So, it'd be good to make sure this patch gets merged somewhere
> that could be used as a baseline for other arm-soc branches if needed,
> to avoid merge conflicts.
I was hoping this could go through the arm-soc tree for the 3.8 merge
window.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2012-10-25 18:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 17:24 [PATCHv2] ARM: Push selects for TWD/SCU into machine entries Stephen Boyd
2012-10-24 17:24 ` Stephen Boyd
2012-10-24 17:54 ` Stephen Warren
2012-10-24 17:54 ` Stephen Warren
2012-10-25 18:04 ` Stephen Boyd [this message]
2012-10-25 18:04 ` Stephen Boyd
2012-10-25 20:34 ` David Brown
2012-10-25 20:34 ` David Brown
-- strict thread matches above, loose matches on Subject: below --
2013-02-27 23:28 Stephen Boyd
2013-02-27 23:28 ` Stephen Boyd
2013-02-27 23:43 ` Stephen Warren
2013-02-27 23:43 ` Stephen Warren
2013-03-05 1:45 ` Stephen Boyd
2013-03-05 1:45 ` Stephen Boyd
2013-03-05 22:34 ` Arnd Bergmann
2013-03-05 22:34 ` Arnd Bergmann
2013-03-16 19:32 ` Stephen Boyd
2013-03-16 19:32 ` Stephen Boyd
2013-03-26 17:34 ` Stephen Boyd
2013-03-26 17:34 ` Stephen Boyd
2013-04-09 16:47 ` Stephen Boyd
2013-04-09 16:47 ` Stephen Boyd
2013-04-09 18:32 ` Arnd Bergmann
2013-04-09 18:32 ` Arnd Bergmann
2013-04-09 19:35 ` Arnd Bergmann
2013-04-09 19:35 ` Arnd Bergmann
2013-04-09 19:35 ` Arnd Bergmann
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=50897F39.9030702@codeaurora.org \
--to=sboyd@codeaurora.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.