From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] Add proper support for Compulab CM-A510/SBC-A510
Date: Mon, 11 May 2015 14:58:08 +0200 [thread overview]
Message-ID: <5550A760.9080200@free-electrons.com> (raw)
In-Reply-To: <2740728.K6gusYnMDt@wuerfel>
Hi Sebastian,
On 06/05/2015 15:13, Arnd Bergmann wrote:
> On Wednesday 06 May 2015 15:06:29 Gregory CLEMENT wrote:
>>
>> On 04/05/2015 22:08, Sebastian Hesselbarth wrote:
>>> This is v2 of the patch set to improve current mainline support for
>>> the Compulab CM-A510 System-on-Module (SoM) and its default Compulab
>>> SBC-A510 base board.
>>>
>>> Compared to v1 [1] there have been the overall changes:
>>> - Drop i2c-mux-pinctrl rework as Wolfram Sang raised concerns with
>>> respect to OF_DYNAMIC. Instead we add i2c-mux-pinctrl node by
>>> default and wait until corresponding driver respects disabled
>>> sub-bus nodes. This will add 3 additional i2c busses to all
>>> Dove based boards, but no functional change with respect to
>>> i2c-0.
>>> - Split patches dealing with arch/arm/boot/dts/Makefile to route
>>> them though arm-soc directly.
>>>
>>> Other patches of v1 have already been taken by MVEBU SoC maintainers
>>> as fixes.
>>>
>>> Patches are based on v4.1-rc1 and are intended for v4.2. All patches
>>> contain appropriate Acked-by's from related maintainers. Patches 3
>>> and 5 should go thought arm-soc directly, the rest can go though
>>> mvebu tree.
>>
>> Usually even the change of the arch/arm/boot/dts/Makefile go to
>> arm-soc through mvebu. For patch 5 it makes sens because if the series
>> is spited then the Makefile could be merged before the new file
>> to build.
>>
>> So unless, Arnd or Olof really want to pick the patches 3 and 5 I will
>> apply the patches 2 to 5 on mvebu/dt.
>>
>> Arnd, Olof, do you agree?
>
> Yes, please pick up all the patches and send them to us with your
> normal pull requests.
patches 2 to 5 applied on mvebu/dt
Thanks,
Gregory
>
> Arnd
>
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2015-05-11 12:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 20:08 [PATCH v2 0/5] Add proper support for Compulab CM-A510/SBC-A510 Sebastian Hesselbarth
2015-05-04 20:08 ` [PATCH v2 1/5] devicetree: vendor-prefixes: Add CompuLab to known vendors Sebastian Hesselbarth
2015-05-04 20:08 ` [PATCH v2 2/5] ARM: dts: dove: Add internal i2c multiplexer node Sebastian Hesselbarth
2015-05-04 20:08 ` [PATCH v2 3/5] ARM: dts: dove: Remove Compulab CM-A510 from Makefile Sebastian Hesselbarth
2015-05-04 20:08 ` [PATCH v2 4/5] ARM: dts: dove: Add proper support for Compulab CM-A510/SBC-A510 Sebastian Hesselbarth
2015-05-04 20:08 ` [PATCH v2 5/5] ARM: dts: dove: Add Compulab SBC-A510 to Makefile Sebastian Hesselbarth
2015-05-06 13:06 ` [PATCH v2 0/5] Add proper support for Compulab CM-A510/SBC-A510 Gregory CLEMENT
2015-05-06 13:13 ` Arnd Bergmann
2015-05-11 12:58 ` Gregory CLEMENT [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=5550A760.9080200@free-electrons.com \
--to=gregory.clement@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).