From: Al Viro <viro@zeniv.linux.org.uk>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
richard -rw- weinberger <richard.weinberger@gmail.com>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: linux-next: Tree for Mar 27
Date: Fri, 27 Mar 2020 17:24:07 +0000 [thread overview]
Message-ID: <20200327172407.GV23230@ZenIV.linux.org.uk> (raw)
In-Reply-To: <425b6d83-53da-15bb-8e7a-158f7c44ffad@infradead.org>
On Fri, Mar 27, 2020 at 08:52:47AM -0700, Randy Dunlap wrote:
> On 3/27/20 1:07 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20200326:
> >
>
> on i386, UML defconfig build fails with: (mostly get_user() variants)
Buggered-by: 1a908babcb144 (x86: replace arch macros from compiler with CONFIG_X86_{32,64})
If the intention is to check i386/x86_64 excluding UML, testing
CONFIG_X86_{32,64} is simpler.
Which is not true, since uml/x86 configs bloody well *do* have CONFIG_X86_{32,64}
defined. See arch/x86/um/Kconfig; and yes, it does need those, as well as
arch/x86/Kconfig.cpu.
next prev parent reply other threads:[~2020-03-27 17:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 8:07 linux-next: Tree for Mar 27 Stephen Rothwell
2020-03-27 15:52 ` Randy Dunlap
2020-03-27 17:24 ` Al Viro [this message]
2020-03-31 2:10 ` linux-next: Tree for Mar 27 (kbuild) Randy Dunlap
2020-03-31 2:26 ` Masahiro Yamada
-- strict thread matches above, loose matches on Subject: below --
2026-03-27 22:06 linux-next: Tree for Mar 27 Mark Brown
2025-03-27 9:05 Stephen Rothwell
2024-03-27 3:06 Stephen Rothwell
2023-03-27 1:17 Stephen Rothwell
2019-03-27 3:50 Stephen Rothwell
2018-03-27 9:02 Stephen Rothwell
2017-03-27 5:29 Stephen Rothwell
2016-03-27 10:28 Stephen Rothwell
2015-03-27 8:26 Stephen Rothwell
2014-03-27 7:30 Stephen Rothwell
2014-03-27 7:30 ` Stephen Rothwell
2013-03-27 5:12 Stephen Rothwell
2013-03-27 5:12 ` Stephen Rothwell
2012-03-27 5:27 Stephen Rothwell
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=20200327172407.GV23230@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=rdunlap@infradead.org \
--cc=richard.weinberger@gmail.com \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.