linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Simon Horman <horms@verge.net.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Magnus Damm <damm@opensource.se>, Olof Johansson <olof@lixom.net>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: linux-next: manual merge of the renesas tree with Linus' tree
Date: Thu, 16 May 2013 16:12:19 +1000	[thread overview]
Message-ID: <20130516161219.cc475a1a7a5c3051672e11bd@canb.auug.org.au> (raw)
In-Reply-To: <20130516050450.GA13842@verge.net.au>

[-- Attachment #1: Type: text/plain, Size: 510 bytes --]

Hi Simon,

On Thu, 16 May 2013 14:04:53 +0900 Simon Horman <horms@verge.net.au> wrote:
>
> Sorry about that. I am working on re-basing my branches on
> top of v3.10-rc1 and I have confirmed that in my current local
> branches the problem you describe is no longer present.
> I plan to push the refreshed branches, including a new next branch
> for linux-next, once a few bug-fix patches have been reviewed.

Excellent, thanks.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-05-16  6:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-16  3:22 linux-next: manual merge of the renesas tree with Linus' tree Stephen Rothwell
2013-05-16  5:04 ` Simon Horman
2013-05-16  6:12   ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-03-12  3:07 Stephen Rothwell
2013-02-27  1:17 Stephen Rothwell
2013-02-27  1:27 ` 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=20130516161219.cc475a1a7a5c3051672e11bd@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=arnd@arndb.de \
    --cc=damm@opensource.se \
    --cc=horms@verge.net.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=olof@lixom.net \
    /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).