From: arnd@arndb•de (Arnd Bergmann)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL] ARM: spear-soc support for 3.5
Date: Sun, 22 Apr 2012 21:38:40 +0000 [thread overview]
Message-ID: <201204222138.40732.arnd@arndb.de> (raw)
In-Reply-To: <4F8E38B8.20907@st.com>
On Wednesday 18 April 2012, Viresh Kumar wrote:
> Hi Arnd/Olof,
>
> The following changes since commit a82c81fb238811d4eea6d36b5e0b4c4dda004982:
>
> Add linux-next specific files for 20120416 (2012-04-16 16:00:03 +1000)
>
> are available in the git repository at:
>
> git://git.stlinux.com/spear/linux-2.6.git spear-v3.5
>
Hi Viresh,
I could not pull this tree, because it was based off linux-next rather
than an -rc release. I have instead rebased the commits for you on top of
v3.4-rc3 and split them into a "dt" and a "pinctrl" part that I've applied
to the respective branches in arm-soc.
Please check that everything still works in my version and next time
when you send a pull request do it on top of an -rc release and split
into topics.
Arnd
prev parent reply other threads:[~2012-04-22 21:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 3:44 [GIT PULL] ARM: spear-soc support for 3.5 Viresh Kumar
2012-04-22 21:38 ` Arnd Bergmann [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=201204222138.40732.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--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