From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: sunxi: Add missing sun4i.dtsi file
Date: Thu, 29 Nov 2012 11:57:10 +0100 [thread overview]
Message-ID: <50B73F86.9080203@free-electrons.com> (raw)
In-Reply-To: <201211261823.52160.arnd@arndb.de>
Hi,
Le 26/11/2012 19:23, Arnd Bergmann a ?crit :
> On Monday 26 November 2012, Stefan Roese wrote:
>> Patch f055f1f6 [ARM: sunxi: Add sun4i and cubieboard support] missed
>> this sun4i.dtsi include file. This patch finally brings it upstream
>> enabling support for sun4i boards.
>>
>> Signed-off-by: Stefan Roese <sr@denx.de>
>> Cc: Arnd Bergmann <arnd@arndb.de>
>> Cc: Maxime Ripard <maxime.ripard@free-electrons.com>
>> ---
>> Arnd, I missed adding this include dtsi file in my last
>> cubieboard/sun4i support patch. Please add this patch
>> to your v3.8 branch.
>
> Hi Stefan,
>
> I've added it to the next/soc branch that contains the earlier patches.
> When you submit a patch for inclusion please always address both Olof
> and me, or cc the arm at kernel.org address that forwards to both of us.
>
> It is also helpful to get patches for one platform only from one person.
> I assume that Maxime is ok with you sending the patch this way, but
> it would be clearer if you send it to him to forward it here, or
> get an 'Acked-by:' tag from him before you send the patch for inclusion.
I'm definitely okay with the change, but yes, I'd prefer to be kept in
the loop :)
Thanks,
Maxime
--
Maxime Ripard, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2012-11-29 10:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 14:46 [PATCH] ARM: sunxi: Add missing sun4i.dtsi file Stefan Roese
2012-11-26 18:23 ` Arnd Bergmann
2012-11-29 10:57 ` Maxime Ripard [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=50B73F86.9080203@free-electrons.com \
--to=maxime.ripard@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 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.