From: srinivas.kandagatla@st.com (Srinivas KANDAGATLA)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/7] ARM:sti: Add STiH415/STiH416 platform and board support
Date: Wed, 26 Jun 2013 10:15:07 +0100 [thread overview]
Message-ID: <51CAB11B.1070209@st.com> (raw)
In-Reply-To: <CAOesGMhsaGcpW80CjBRtwVjJLOaRj8yTa6xFz_gjG1WPqTAKLQ@mail.gmail.com>
On 25/06/13 21:47, Olof Johansson wrote:
> On Tue, Jun 25, 2013 at 1:30 PM, Olof Johansson <olof@lixom.net> wrote:
>> On Tue, Jun 25, 2013 at 12:13:42PM +0100, Srinivas KANDAGATLA wrote:
>>> From: Srinivas Kandagatla <srinivas.kandagatla@st.com>
>>>
>>> This patch-set adds basic support for STMicroelectronics STi series SOCs
>>> which includes STiH415 and STiH416 with B2000 and B2020 board support.
>>>
>>> STiH415 and STiH416 are dual-core ARM Cortex-A9 CPU, designed for use in
>>> Set-top-boxes. The SOC support is available in mach-sti which contains
>>> support code for STiH415, STiH416 SOCs including the generic board support.
>>>
>>> The reason for adding two SOCs at this patch set is to show that no new
>>> C code is required for second SOC(STiH416) support.
>>>
>>> This patch-set only contains the SOC support, all the driver support for
>>> this platform are submitted to respective mailing lists.
>>>
>>> Changes since v4:
>>> - Renamed mach-stixxxx to mach-sti as suggested by Olof J.
>>
>> Thanks!
>>
>> I've merged this into next/late, and I'll drop the previous test merge by Arnd
>> of the last version of the patch set.
>
Thanks Olof.
> I noticed that the defconfig update contained new drivers/options that
> won't make it into 3.11. So to avoid churn, I dropped those. We'll do
> a patch to enable all new platforms and drivers towards the end of the
> merge window and apply on top of next/late, I think, so it should be
> taken care of by that.
Ok..
>
> The rest of the code from the series is in though.
>
> -Olof
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Srinivas KANDAGATLA <srinivas.kandagatla@st.com>
To: Olof Johansson <olof@lixom.net>
Cc: Russell King <linux@arm.linux.org.uk>,
kernel@stlinux.com, Arnd Bergmann <arnd@arndb.de>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Stephen Gallimore <stephen.gallimore@st.com>,
Stuart Menefy <stuart.menefy@st.com>,
Rob Landley <rob@landley.net>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v5 0/7] ARM:sti: Add STiH415/STiH416 platform and board support
Date: Wed, 26 Jun 2013 10:15:07 +0100 [thread overview]
Message-ID: <51CAB11B.1070209@st.com> (raw)
In-Reply-To: <CAOesGMhsaGcpW80CjBRtwVjJLOaRj8yTa6xFz_gjG1WPqTAKLQ@mail.gmail.com>
On 25/06/13 21:47, Olof Johansson wrote:
> On Tue, Jun 25, 2013 at 1:30 PM, Olof Johansson <olof@lixom.net> wrote:
>> On Tue, Jun 25, 2013 at 12:13:42PM +0100, Srinivas KANDAGATLA wrote:
>>> From: Srinivas Kandagatla <srinivas.kandagatla@st.com>
>>>
>>> This patch-set adds basic support for STMicroelectronics STi series SOCs
>>> which includes STiH415 and STiH416 with B2000 and B2020 board support.
>>>
>>> STiH415 and STiH416 are dual-core ARM Cortex-A9 CPU, designed for use in
>>> Set-top-boxes. The SOC support is available in mach-sti which contains
>>> support code for STiH415, STiH416 SOCs including the generic board support.
>>>
>>> The reason for adding two SOCs at this patch set is to show that no new
>>> C code is required for second SOC(STiH416) support.
>>>
>>> This patch-set only contains the SOC support, all the driver support for
>>> this platform are submitted to respective mailing lists.
>>>
>>> Changes since v4:
>>> - Renamed mach-stixxxx to mach-sti as suggested by Olof J.
>>
>> Thanks!
>>
>> I've merged this into next/late, and I'll drop the previous test merge by Arnd
>> of the last version of the patch set.
>
Thanks Olof.
> I noticed that the defconfig update contained new drivers/options that
> won't make it into 3.11. So to avoid churn, I dropped those. We'll do
> a patch to enable all new platforms and drivers towards the end of the
> merge window and apply on top of next/late, I think, so it should be
> taken care of by that.
Ok..
>
> The rest of the code from the series is in though.
>
> -Olof
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
>
next prev parent reply other threads:[~2013-06-26 9:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 11:13 [PATCH v5 0/7] ARM:sti: Add STiH415/STiH416 platform and board support Srinivas KANDAGATLA
2013-06-25 11:13 ` Srinivas KANDAGATLA
2013-06-25 11:15 ` [PATCH v5 1/7] ARM:sti: Add STiH415 SOC support Srinivas KANDAGATLA
2013-06-25 11:15 ` Srinivas KANDAGATLA
2013-06-25 11:15 ` [PATCH v5 2/7] ARM:sti: Add STiH416 " Srinivas KANDAGATLA
2013-06-25 11:15 ` Srinivas KANDAGATLA
2013-06-25 11:15 ` [PATCH v5 3/7] ARM:sti: Add DEBUG_LL console support Srinivas KANDAGATLA
2013-06-25 11:15 ` Srinivas KANDAGATLA
2013-06-25 11:15 ` [PATCH v5 4/7] ARM:multi_v7_defconfig: rerun savedefconfig Srinivas KANDAGATLA
2013-06-25 11:15 ` Srinivas KANDAGATLA
2013-06-25 11:15 ` [PATCH v5 5/7] ARM:sti: Add sti options to multi_v7_defconfig Srinivas KANDAGATLA
2013-06-25 11:15 ` Srinivas KANDAGATLA
2013-06-25 11:16 ` [PATCH v5 6/7] ARM:stih41x: Add B2000 board support Srinivas KANDAGATLA
2013-06-25 11:16 ` Srinivas KANDAGATLA
2013-06-25 11:16 ` [PATCH v5 7/7] ARM:stih41x: Add B2020 " Srinivas KANDAGATLA
2013-06-25 11:16 ` Srinivas KANDAGATLA
2013-06-25 20:30 ` [PATCH v5 0/7] ARM:sti: Add STiH415/STiH416 platform and " Olof Johansson
2013-06-25 20:30 ` Olof Johansson
2013-06-25 20:47 ` Olof Johansson
2013-06-25 20:47 ` Olof Johansson
2013-06-26 9:15 ` Srinivas KANDAGATLA [this message]
2013-06-26 9:15 ` Srinivas KANDAGATLA
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=51CAB11B.1070209@st.com \
--to=srinivas.kandagatla@st.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 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.