From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Borislav Petkov <bp@suse.de>
Cc: linaro-kernel@lists.linaro.org,
kernel-build-reports@lists.linaro.org,
Peter Zijlstra <peterz@infradead.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Mark Brown <broonie@kernel.org>,
linux-next@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: next-20181008 build: 2 failures 22 warnings (next-20181008)
Date: Fri, 12 Oct 2018 13:43:57 +1100 [thread overview]
Message-ID: <20181012134357.51bfd026@canb.auug.org.au> (raw)
In-Reply-To: <20181012103758.51c7befa@canb.auug.org.au>
[-- Attachment #1.1: Type: text/plain, Size: 829 bytes --]
Hi Boris,
On Fri, 12 Oct 2018 10:37:58 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> On Wed, 10 Oct 2018 06:33:59 +0200 Borislav Petkov <bp@suse.de> wrote:
> >
> > On Wed, Oct 10, 2018 at 03:27:04PM +1100, Stephen Rothwell wrote:
> > > I have added that to linux-next today (pending this or something else
> > > turning up in the tip tree).
> >
> > I have queued a fixed version in the meantime:
> >
> > https://git.kernel.org/tip/9d94e8b1d4f94a3c4cee5ad11a1be460cd070839
>
> OK, I will use that until it turns up in the tip auto-latest branch.
It turns out that I can't use that since it is mostly already in the
tip tree as commit
3a387c6d96e6 ("x86/kaslr, ACPI/NUMA: Fix KASLR build error")
So I will stick with my incremental patch for now.
--
Cheers,
Stephen Rothwell
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-10-12 2:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1g9cV0-0008Sg-4U@optimist>
2018-10-08 21:11 ` next-20181008 build: 2 failures 22 warnings (next-20181008) Mark Brown
2018-10-08 21:30 ` Borislav Petkov
2018-10-10 4:27 ` Stephen Rothwell
2018-10-10 4:33 ` Borislav Petkov
2018-10-11 23:37 ` Stephen Rothwell
2018-10-12 2:43 ` Stephen Rothwell [this message]
2018-10-08 21:20 ` Mark Brown
2018-10-08 21:30 ` Bjorn Helgaas
2018-10-08 22:35 ` Mark Brown
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=20181012134357.51bfd026@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bp@suse.de \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=will.deacon@arm.com \
/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