From: Stephen Rothwell <sfr@canb.auug.org.au>
To: James Hogan <james.hogan@imgtec.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Arnd <arnd@arndb.de>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] late arch/metag fixes for v3.9-rc1
Date: Sun, 3 Mar 2013 02:48:51 +1100 [thread overview]
Message-ID: <20130303024851.4be2d2435da42a6010c6c8f8@canb.auug.org.au> (raw)
In-Reply-To: <5131D2F0.2010705@imgtec.com>
[-- Attachment #1: Type: text/plain, Size: 598 bytes --]
Hi James,
On Sat, 2 Mar 2013 10:22:40 +0000 James Hogan <james.hogan@imgtec.com> wrote:
>
> Okay, I've rebased the arch/metag tree onto mainline to make all the
> back-merges unnecessary and applied those simple fixes into "Build
> infrastructure" and "Various other headers" commits (additionally
> trivially removing ARCH_NO_VIRT_TO_BUS which is also now unnecessary).
Pleas make sure that what you are submitting to Linus is the same as what
you have in linux-next (i.e. reset your for-next branch as well).
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-03-02 15:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 16:55 [GIT PULL] late arch/metag fixes for v3.9-rc1 James Hogan
2013-03-01 18:03 ` Linus Torvalds
2013-03-01 18:54 ` James Hogan
2013-03-02 10:22 ` James Hogan
2013-03-02 15:48 ` Stephen Rothwell [this message]
2013-03-02 16:22 ` James Hogan
2013-03-03 2:11 ` Stephen Rothwell
2013-03-02 16:28 ` Linus Torvalds
2013-03-02 16:31 ` Linus Torvalds
2013-03-02 18:10 ` Borislav Petkov
2013-03-02 18:40 ` Linus Torvalds
2013-03-02 19:19 ` Borislav Petkov
2013-03-02 19:25 ` Linus Torvalds
2013-03-02 19:06 ` Raymond Jennings
2013-03-02 19:05 ` James Hogan
2013-03-02 21:40 ` James Hogan
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=20130303024851.4be2d2435da42a6010c6c8f8@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=arnd@arndb.de \
--cc=james.hogan@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).