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-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
Subject: Re: [PATCH v4 0/7] ARM:STixxxx: Add STixxxx platform and board support
Date: Tue, 25 Jun 2013 07:53:47 +0100 [thread overview]
Message-ID: <51C93E7B.30709@st.com> (raw)
In-Reply-To: <20130624175415.GA31429@quad.lixom.net>
On 24/06/13 18:54, Olof Johansson wrote:
> On Fri, Jun 21, 2013 at 11:37:56AM +0100, Srinivas KANDAGATLA wrote:
>> From: Srinivas Kandagatla <srinivas.kandagatla@st.com>
>>
>> Thankyou all for reviewing the v3 patches.
>>
>> This patch-set adds basic support for STMicroelectronics STixxxx 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-stixxxx 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.
>
> Hi,
>
> I think these are looking quite reasonable, and I am ready to apply them
> to 3.11.
>
> However, I have one bikeshed comment. I find the name of the platform to be
> awkward. Would you mind naming it mach-sti instead?
Am OK to rename them,
But, I see the patches on arm-soc for-next branch.
Thanks,
srini
>
>
> -Olof
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
prev parent reply other threads:[~2013-06-25 6:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 10:37 [PATCH v4 0/7] ARM:STixxxx: Add STixxxx platform and board support Srinivas KANDAGATLA
2013-06-21 10:39 ` [PATCH v4 1/7] ARM:stixxxx: Add STiH415 SOC support Srinivas KANDAGATLA
2013-06-21 10:39 ` [PATCH v4 2/7] ARM:stixxxx: Add STiH416 " Srinivas KANDAGATLA
2013-06-21 10:39 ` [PATCH v4 3/7] ARM:stixxxx: Add DEBUG_LL console support Srinivas KANDAGATLA
2013-06-21 10:39 ` [PATCH v4 4/7] ARM:multi_v7_defconfig: rerun savedefconfig Srinivas KANDAGATLA
2013-06-21 10:39 ` [PATCH v4 5/7] ARM:stixxxx: Add stixxxx options to multi_v7_defconfig Srinivas KANDAGATLA
2013-06-21 10:39 ` [PATCH v4 6/7] ARM:stih41x: Add B2000 board support Srinivas KANDAGATLA
2013-06-21 10:39 ` [PATCH v4 7/7] ARM:stih41x: Add B2020 " Srinivas KANDAGATLA
2013-06-24 17:54 ` [PATCH v4 0/7] ARM:STixxxx: Add STixxxx platform and " Olof Johansson
2013-06-25 6:53 ` Srinivas KANDAGATLA [this message]
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=51C93E7B.30709@st.com \
--to=srinivas.kandagatla@st.com \
--cc=arnd@arndb.de \
--cc=kernel@stlinux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=olof@lixom.net \
--cc=rob@landley.net \
--cc=stephen.gallimore@st.com \
--cc=stuart.menefy@st.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