From: gregory.clement@free-electrons•com (Gregory CLEMENT)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v9] arm: Add basic support for new Marvell Armada 370 and Armada XP SoC
Date: Tue, 10 Jul 2012 14:18:45 +0200 [thread overview]
Message-ID: <4FFC1DA5.6050805@free-electrons.com> (raw)
In-Reply-To: <201207101203.30984.arnd@arndb.de>
On 07/10/2012 02:03 PM, Arnd Bergmann wrote:
> On Tuesday 10 July 2012, Thomas Petazzoni wrote:
>> Le Fri, 6 Jul 2012 17:23:32 +0200,
>> Thomas Petazzoni <thomas.petazzoni@free-electrons•com> a ?crit :
>>
>>> You'll find in this patch set the nineth version of the initial
>>> support for a new family of ARMv7-compatible Marvell SoCs.
>>
>> This v9 version has received Acked-by from Andrew Lunn on the
>> different patches, we have solved the maintainership question of the
>> new mach-mvebu directory, and so far there hasn't been additional
>> comments on this v9.
>>
>> Is there anything we can do to help in getting this patch set merged?
>
> Usually I'm waiting for git pull requests, which fits the arm-soc
> workflow best, but it's also ok to ask for patches to be included,
> especially if you do not have a public git tree.
>
> Should I apply the patches to a new branch in arm-soc or do you
> send a pull request?
>
We have a public git tree available at:
https://github.com/Marvell-Semi/EBU_mainline_public.git
this last patch set is directly from mvebu_for-next-V9 branch.
Do you need a formal request?
> Arnd
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-07-10 12:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 15:23 [PATCH v9] arm: Add basic support for new Marvell Armada 370 and Armada XP SoC Thomas Petazzoni
2012-07-06 15:23 ` [PATCH v9 1/9] clocksource: time-armada-370-xp: Marvell Armada 370/XP SoC timer driver Thomas Petazzoni
2012-07-18 23:48 ` John Stultz
2012-07-18 23:51 ` John Stultz
2012-07-19 1:41 ` Nicolas Pitre
2012-07-19 3:57 ` John Stultz
2012-07-06 15:23 ` [PATCH v9 2/9] arm: mach-mvebu: add header Thomas Petazzoni
2012-07-06 15:23 ` [PATCH v9 3/9] arm: mach-mvebu: add source files Thomas Petazzoni
2012-07-06 15:23 ` [PATCH v9 4/9] arm: mach-mvebu: add support for Armada 370 and Armada XP with DT Thomas Petazzoni
2012-07-06 15:23 ` [PATCH v9 5/9] arm: mach-mvebu: add documentation for new device tree bindings Thomas Petazzoni
2012-07-06 15:23 ` [PATCH v9 6/9] arm: mach-mvebu: add defconfig Thomas Petazzoni
2012-07-06 15:23 ` [PATCH v9 7/9] arm: mach-mvebu: add compilation/configuration change Thomas Petazzoni
2012-07-06 15:23 ` [PATCH v9 8/9] arm: mach-mvebu: add entry to MAINTAINERS Thomas Petazzoni
2012-07-06 15:23 ` [PATCH v9 9/9] ARM: mvebu: MPIC: read number of interrupts from control register Thomas Petazzoni
2012-07-10 9:16 ` [PATCH v9] arm: Add basic support for new Marvell Armada 370 and Armada XP SoC Thomas Petazzoni
2012-07-10 12:03 ` Arnd Bergmann
2012-07-10 12:18 ` Gregory CLEMENT [this message]
2012-07-10 14:01 ` Arnd Bergmann
2012-07-10 14:12 ` Gregory CLEMENT
2012-07-20 14:21 ` Ian Molton
2012-07-20 17:02 ` 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=4FFC1DA5.6050805@free-electrons.com \
--to=gregory.clement@free-electrons$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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