All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
	Russell King <rmk@arm.linux.org.uk>,
	Thomas Gleixner <tglx@linutronix.de>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86_32: add support for 64 bit __get_user() v3
Date: Mon, 14 Mar 2016 17:39:26 +0100	[thread overview]
Message-ID: <20160314163926.GB19628@gmail.com> (raw)
In-Reply-To: <20160314153747.GH17923@kvack.org>


* Benjamin LaHaise <bcrl@kvack.org> wrote:

> Any more comments/feedback on this?  Can this be merged for 4.6?

Will get to it once the merge window calms down.

Thanks,

	Ingo

  reply	other threads:[~2016-03-14 16:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09 17:22 [PATCH] x86_32: add support for 64 bit __get_user() Benjamin LaHaise
2016-03-09 17:36 ` H. Peter Anvin
2016-03-09 17:50   ` Benjamin LaHaise
2016-03-09 18:22     ` H. Peter Anvin
2016-03-09 18:27       ` Benjamin LaHaise
2016-03-09 19:30       ` [PATCH] x86_32: add support for 64 bit __get_user() v2 Benjamin LaHaise
2016-03-09 19:41         ` kbuild test robot
2016-03-09 20:05         ` [PATCH] x86_32: add support for 64 bit __get_user() v3 Benjamin LaHaise
2016-03-14 15:37           ` Benjamin LaHaise
2016-03-14 16:39             ` Ingo Molnar [this message]
2016-03-09 20:24         ` [PATCH] x86_32: add support for 64 bit __get_user() v2 kbuild test robot
2016-03-09 18:17 ` [PATCH] x86_32: add support for 64 bit __get_user() kbuild test robot
2016-03-09 18:22 ` kbuild test robot
2016-03-09 18:23 ` kbuild test robot

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=20160314163926.GB19628@gmail.com \
    --to=mingo@kernel.org \
    --cc=bcrl@kvack.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rmk@arm.linux.org.uk \
    --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 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.