From: sfr@canb.auug.org.au (Stephen Rothwell)
To: linux-arm-kernel@lists.infradead.org
Subject: next-20160503 build: 1 failures 12 warnings (next-20160503)
Date: Tue, 10 May 2016 04:36:43 +1000 [thread overview]
Message-ID: <20160510043643.1a680d26@canb.auug.org.au> (raw)
In-Reply-To: <CACRpkdbuJym-7tSMo1gXyWvGCRvvuor8EeCK2bm6=Kb20vTxNA@mail.gmail.com>
Hi Linus,
On Mon, 9 May 2016 15:12:51 +0200 Linus Walleij <linus.walleij@linaro.org> wrote:
>
> On Mon, May 9, 2016 at 12:53 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> > Can we, please, get this fixed ... less than a week to the merge window
> > opening ...
>
> Mark poked me with a sharp stick, the patch is applied!
> Sorry for missing this.
Thanks.
--
Cheers,
Stephen Rothwell
prev parent reply other threads:[~2016-05-09 18:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1axZpG-000664-AK@optimist>
2016-05-03 14:17 ` next-20160503 build: 1 failures 12 warnings (next-20160503) Mark Brown
2016-05-03 15:02 ` Arnd Bergmann
2016-05-09 10:53 ` Stephen Rothwell
2016-05-09 11:17 ` Arnd Bergmann
2016-05-09 18:29 ` Stephen Rothwell
2016-05-09 13:12 ` Linus Walleij
2016-05-09 18:36 ` 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=20160510043643.1a680d26@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--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).