From: Ingo Molnar <mingo@kernel•org>
To: Kees Cook <keescook@chromium•org>
Cc: Ard Biesheuvel <ardb@kernel•org>,
Stephen Rothwell <sfr@canb•auug.org.au>,
Arvind Sankar <nivedita@alum•mit.edu>,
Thomas Gleixner <tglx@linutronix•de>, Ingo Molnar <mingo@elte•hu>,
"H. Peter Anvin" <hpa@zytor•com>,
Peter Zijlstra <peterz@infradead•org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: new build warnings after binutils update
Date: Sat, 15 Aug 2020 20:14:57 +0200 [thread overview]
Message-ID: <20200815181457.GA2719638@gmail.com> (raw)
In-Reply-To: <202008141232.A5A5D8C7@keescook>
* Kees Cook <keescook@chromium•org> wrote:
> On Fri, Aug 14, 2020 at 12:22:06PM +0200, Ingo Molnar wrote:
> > > [0] https://lore.kernel.org/lkml/20200731202738.2577854-6-nivedita@alum.mit.edu/
> >
> > It all looked good to me but was a bit late for v5.9, will pick up
> > after -rc1.
>
> Excellent! Thank you. I'll base the orphan series on x86/boot now. Once
> I send a v6 (there are a few more things to tweak), can you carry that
> in -tip as well (it includes arm and arm64 as well, all of which depend
> on several asm-generic patches).
Sure, that looks the most sensible, since there's so much x86 impact.
Might migrate the commits over into a more generic topic branch -
started out with x86/boot to get things going.
Thanks,
Ingo
prev parent reply other threads:[~2020-08-15 22:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 4:31 linux-next: new build warnings after binutils update Stephen Rothwell
2020-08-14 7:05 ` Ard Biesheuvel
2020-08-14 10:22 ` Ingo Molnar
2020-08-14 10:24 ` Ard Biesheuvel
2020-08-14 14:03 ` Sedat Dilek
2020-08-14 19:33 ` Kees Cook
2020-08-15 18:14 ` Ingo Molnar [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=20200815181457.GA2719638@gmail.com \
--to=mingo@kernel$(echo .)org \
--cc=ardb@kernel$(echo .)org \
--cc=hpa@zytor$(echo .)com \
--cc=keescook@chromium$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=nivedita@alum$(echo .)mit.edu \
--cc=peterz@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tglx@linutronix$(echo .)de \
/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