From: Mark Brown <broonie@kernel•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linaro-kernel@lists•linaro.org,
kernel-build-reports@lists•linaro.org,
Marc Zyngier <marc.zyngier@arm•com>,
Catalin Marinas <catalin.marinas@arm•com>,
Will Deacon <will.deacon@arm•com>,
linux-next@vger•kernel.org, linux-arm-kernel@lists•infradead.org,
kvmarm@lists•cs.columbia.edu
Subject: Re: next-20160222 build: 5 failures 9 warnings (next-20160222)
Date: Wed, 24 Feb 2016 13:16:44 +0900 [thread overview]
Message-ID: <20160224041644.GS18327@sirena.org.uk> (raw)
In-Reply-To: <20160224144859.027a3564@canb.auug.org.au>
[-- Attachment #1.1: Type: text/plain, Size: 456 bytes --]
On Wed, Feb 24, 2016 at 02:48:59PM +1100, Stephen Rothwell wrote:
> On Wed, 24 Feb 2016 12:28:42 +0900 Mark Brown <broonie@kernel•org> wrote:
> > That didn't work out unfortunately, the error is still there today.
> Yeah, the patch didn't hit -next yesterday and I missed the opportunity
> to fix in manually. However, it should be fixed in today's linux-next
> (out in a few hours, hopefully).
Ah, good - it was just too late rather than not working.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 151 bytes --]
_______________________________________________
kvmarm mailing list
kvmarm@lists•cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
next prev parent reply other threads:[~2016-02-24 4:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 8:36 next-20160222 build: 5 failures 9 warnings (next-20160222) Build bot for Mark Brown
2016-02-22 10:08 ` Mark Brown
2016-02-22 10:41 ` Marc Zyngier
2016-02-22 11:52 ` Brian Starkey
2016-02-22 12:00 ` Marc Zyngier
2016-02-22 12:07 ` Brian Starkey
2016-02-22 12:44 ` Marc Zyngier
2016-02-22 13:19 ` Stephen Rothwell
2016-02-24 3:28 ` Mark Brown
2016-02-24 3:48 ` Stephen Rothwell
2016-02-24 4:16 ` Mark Brown [this message]
2016-02-22 10:19 ` Mark Brown
2016-02-22 10:25 ` Mark Brown
2016-02-22 10:37 ` Jean-Philippe Brucker
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=20160224041644.GS18327@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=catalin.marinas@arm$(echo .)com \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=kvmarm@lists$(echo .)cs.columbia.edu \
--cc=linaro-kernel@lists$(echo .)linaro.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=marc.zyngier@arm$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=will.deacon@arm$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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