public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben.hutchings@codethink.co.uk>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: 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 16:31:03 +0000	[thread overview]
Message-ID: <1521649863.23626.130.camel@codethink.co.uk> (raw)
In-Reply-To: <20180321160424.GF18454@kroah.com>

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").

Ben.

-- 
Ben Hutchings
Software Developer, Codethink Ltd.

  reply	other threads:[~2018-03-21 16:31 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 [this message]
2018-03-21 16:34     ` Lennart Sorensen
2018-03-21 16:37       ` 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=1521649863.23626.130.camel@codethink.co.uk \
    --to=ben.hutchings@codethink.co.uk \
    --cc=gregkh@linuxfoundation.org \
    --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