From: Olof Johansson <olof@lixom.net>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] Renesas ARM and SH based SoC pinmux fixes for v3.10 #2
Date: Tue, 28 May 2013 02:28:40 +0000 [thread overview]
Message-ID: <20130528022840.GA13532@quad.lixom.net> (raw)
In-Reply-To: <1369461157-19256-1-git-send-email-horms+renesas@verge.net.au>
On Sat, May 25, 2013 at 02:52:36PM +0900, Simon Horman wrote:
> Hi Arnd, Hi Olof,
>
> The following changes since commit c7788792a5e7b0d5d7f96d0766b4cb6112d47d75:
>
> Linux 3.10-rc2 (2013-05-20 14:37:38 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-pinmux-fixes2-for-v3.10
Hi Simon,
For fixes, especially if you have only one per branch, please just
send one pull so we don't get a crazy number of merge changesets in the
history. We don't split them into categories during -rcs.
-Olof
next parent reply other threads:[~2013-05-28 2:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1369461157-19256-1-git-send-email-horms+renesas@verge.net.au>
2013-05-28 2:28 ` Olof Johansson [this message]
2013-05-28 5:37 ` [GIT PULL] Renesas ARM and SH based SoC pinmux fixes for v3.10 #2 Simon Horman
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=20130528022840.GA13532@quad.lixom.net \
--to=olof@lixom.net \
--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).