From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable <stable@vger.kernel.org>, Sasha Levin <sashal@kernel.org>
Subject: Re: Build failure in v4.4.y-queue
Date: Sun, 16 Jun 2019 17:24:07 +0200 [thread overview]
Message-ID: <20190616152407.GB16197@kroah.com> (raw)
In-Reply-To: <88e25ca4-9e77-74b7-4466-2477cb07ce20@roeck-us.net>
On Sun, Jun 16, 2019 at 07:01:57AM -0700, Guenter Roeck wrote:
> Building um:defconfig ... failed
> --------------
> Error log:
> kernel/time/Kconfig:155:warning: range is invalid
> /opt/buildbot/slave/stable-queue-4.4/build/arch/um/kernel/time.c:59:14: error: initializer element is not constant
> .cpumask = cpu_possible_mask,
>
> Caused by commit 502482cde8ab ("uml: fix a boot splat wrt use of cpu_all_mask"),
> which fixes a problem which does not exist in v4.4.y.
Now dropped, thanks.
greg k-h
next prev parent reply other threads:[~2019-06-16 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-16 14:01 Build failure in v4.4.y-queue Guenter Roeck
2019-06-16 15:24 ` Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-30 14:44 Guenter Roeck
2019-01-30 14:47 ` Greg Kroah-Hartman
2019-01-31 7:55 ` Greg Kroah-Hartman
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=20190616152407.GB16197@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux@roeck-us.net \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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).