From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Ben Hutchings <ben.hutchings@codethink.co.uk>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 4.9.80 compile failure with X86_VSYSCALL_EMULATION=n due to 9a0be5af
Date: Wed, 21 Mar 2018 17:37:38 +0100 [thread overview]
Message-ID: <20180321163738.GA5269@kroah.com> (raw)
In-Reply-To: <20180321163438.7q37vh7pncljib2a@csclub.uwaterloo.ca>
On Wed, Mar 21, 2018 at 12:34:38PM -0400, Lennart Sorensen wrote:
> On Wed, Mar 21, 2018 at 04:31:03PM +0000, Ben Hutchings wrote:
> > On Wed, 2018-03-21 at 17:04 +0100, Greg Kroah-Hartman wrote:
> > > On Mon, Feb 12, 2018 at 10:43:25AM -0500, Lennart Sorensen wrote:
> > > > Commit 9a0be5af added a reference to vsyscall_pgprot in
> > > > arch/x86/mm/kaiser.c but that is undefined if X86_VSYSCALL_EMULATION=n
> > > > which on an embedded system where you know how all your software is
> > > > compiled is quite likely.
> > > >
> > > > Of course the condition is always false with that config so the code
> > > > will never be run, but the compiler is unhappy.
> > >
> > > What is the compiler error? I have not had any reports of this with all
> > > of the varied builds that we currently run on the stable trees.
> >
> > You already applied a fix for this ("kaiser: fix compile error without
> > vsyscall").
>
> Yeah the fix certainly works fine. I was not the only one reporting it.
Ah, ok, sorry, was catching up on email...
greg k-h
prev parent reply other threads:[~2018-03-21 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 15:43 4.9.80 compile failure with X86_VSYSCALL_EMULATION=n due to 9a0be5af Lennart Sorensen
2018-03-21 16:04 ` Greg Kroah-Hartman
2018-03-21 16:31 ` Ben Hutchings
2018-03-21 16:34 ` Lennart Sorensen
2018-03-21 16:37 ` Greg Kroah-Hartman [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=20180321163738.GA5269@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ben.hutchings@codethink.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
/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