From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu soc changes for v3.15
Date: Fri, 21 Feb 2014 19:59:00 -0500 [thread overview]
Message-ID: <20140222005900.GP7862@titan.lakedaemon.net> (raw)
In-Reply-To: <20140222003415.GE13233@quad.lixom.net>
On Fri, Feb 21, 2014 at 04:34:15PM -0800, Olof Johansson wrote:
> On Tue, Feb 18, 2014 at 11:36:28AM -0500, Jason Cooper wrote:
> > All,
> >
> > A small round of changes that have been sitting in -next for a week or
> > so. Please pull.
> >
> > thx,
> >
> > Jason.
> >
> >
> > The following changes since commit 38dbfb59d1175ef458d006556061adeaa8751b72:
> >
> > Linus 3.14-rc1 (2014-02-02 16:42:13 -0800)
> >
> > are available in the git repository at:
> >
> > git://git.infradead.org/linux-mvebu.git tags/mvebu-soc-3.15
> >
> > for you to fetch changes up to 08bb3adfd3adeb4653095e7968b6a46cef940404:
> >
> > ARM: mvebu: remove unneeded ->map_io field for Armada 370/XP (2014-02-11 19:33:04 +0000)
>
> Thanks, merged into next/cleanup.
Heads up: I'm currently basing mvebu/soc-3xx on top of this work to
avoid keeping track of a tricky modify/rename merge. Namely, removing
map_io in the above, and the mvebu/soc-3xx branch renames the same file.
As long as you don't mind having a branch depending on next/cleanup, all
should be good. No action required.
I'd've mentioned it in the pull request, but we just discovered it today
and I did the rebase 5 minutes ago. :)
thx,
Jason.
next prev parent reply other threads:[~2014-02-22 0:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 16:36 [GIT PULL] ARM: mvebu soc changes for v3.15 Jason Cooper
2014-02-22 0:34 ` Olof Johansson
2014-02-22 0:59 ` Jason Cooper [this message]
2014-02-22 1:00 ` 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=20140222005900.GP7862@titan.lakedaemon.net \
--to=jason@lakedaemon.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