public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
	the arch/x86 maintainers <x86@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/mm/kaiser: avoid 32-bit/PAE build warning
Date: Wed, 6 Dec 2017 18:16:13 +0100	[thread overview]
Message-ID: <20171206171612.v5ucbi6yyeiks2yv@gmail.com> (raw)
In-Reply-To: <CAK8P3a0vNfGhe3LuoMFnWc5JDTwJuFhu3EBAqK56TZBX5D8zBQ@mail.gmail.com>


* Arnd Bergmann <arnd@arndb.de> wrote:

> On Wed, Dec 6, 2017 at 4:08 PM, Dave Hansen <dave.hansen@linux.intel.com> wrote:
> > On 12/06/2017 07:03 AM, Arnd Bergmann wrote:
> >> On Wed, Dec 6, 2017 at 3:15 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> >>
> >> Maybe it's better to just to the last one-line change in include/linux/kaiser.h.
> >
> > Hi Arnd,
> >
> > Are you hitting this in -next?
> >
> > The newest version of this code has a single kpti_init() function that
> > shouldn't have any of these problems.
> 
> Yes, this is next-20171206, apparently it came in through tip/auto-latest,
> which still has the same version.

I'll update the -next version probably later today.

Thanks,

	Ingo

  reply	other threads:[~2017-12-06 17:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06 14:15 [PATCH] x86/mm/kaiser: avoid 32-bit/PAE build warning Arnd Bergmann
2017-12-06 15:03 ` Arnd Bergmann
2017-12-06 15:08   ` Dave Hansen
2017-12-06 16:36     ` Arnd Bergmann
2017-12-06 17:16       ` Ingo Molnar [this message]
2017-12-06 20:47         ` Arnd Bergmann
2017-12-06 21:02           ` Ingo Molnar
2018-02-14 22:12     ` Arnd Bergmann
2018-02-15  5:43       ` Greg KH
2018-02-15 15:37         ` Arnd Bergmann
2018-02-15 16:43           ` Greg KH
2018-02-15 21:00             ` Arnd Bergmann
2018-02-19 10:04               ` Arnd Bergmann

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=20171206171612.v5ucbi6yyeiks2yv@gmail.com \
    --to=mingo@kernel.org \
    --cc=arnd@arndb.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=x86@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