linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mark Brown <broonie@kernel.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for 3rd December
Date: Mon, 7 Dec 2015 09:46:43 +1100	[thread overview]
Message-ID: <20151207094643.6e8df411@canb.auug.org.au> (raw)
In-Reply-To: <20151203233143.GI5727@sirena.org.uk>

Hi Mark,

On Thu, 3 Dec 2015 23:31:43 +0000 Mark Brown <broonie@kernel.org> wrote:
>
> It is very unlikely that there will be a build tomorrow, Stephen will be
> back and -next will be back to normal on Monday.

Thank you very much for taking this on again.  I am back and hopefully
will be able to take over from where you got to.

I will try very hard not to send emails about the conflicts/build
problems you have already noted, but there may be some overlap.

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

      reply	other threads:[~2015-12-06 22:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-03 23:31 linux-next: Tree for 3rd December Mark Brown
2015-12-06 22:46 ` Stephen Rothwell [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=20151207094643.6e8df411@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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).