From: maxime.ripard@free-electrons•com (Maxime Ripard)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL] ARM: arm-soc fixes for 3.8
Date: Tue, 18 Dec 2012 16:01:27 +0100 [thread overview]
Message-ID: <50D08547.8040405@free-electrons.com> (raw)
In-Reply-To: <20121218065502.GA12865@quad.lixom.net>
Hi Olof,
Le 18/12/2012 07:55, Olof Johansson a ?crit :
> Maxime Ripard (1):
> ARM: sunxi: Change device tree naming scheme for sunxi
There's something odd about this one (commit 68136b10). The patch that
you seem to have applied differs from the one I sent. The DTs files
appears to have not been renamed, while in the patch I sent
(http://lists.infradead.org/pipermail/linux-arm-kernel/2012-December/137105.html),
it's the case.
Do you know what happened here? What can we do to fix that?
Maxime
--
Maxime Ripard, 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-12-18 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 6:55 [GIT PULL] ARM: arm-soc fixes for 3.8 Olof Johansson
2012-12-18 15:01 ` Maxime Ripard [this message]
2012-12-18 15:21 ` Olof Johansson
2012-12-20 15:10 ` Tony Lindgren
2012-12-20 16:29 ` Olof Johansson
-- strict thread matches above, loose matches on Subject: below --
2013-02-12 19:22 Olof Johansson
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=50D08547.8040405@free-electrons.com \
--to=maxime.ripard@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