All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Stefani Seibold <stefani@seibold.net>,
	Greg KH <gregkh@linuxfoundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	X86 ML <x86@kernel.org>, Ingo Molnar <mingo@redhat.com>,
	Andi Kleen <ak@linux.intel.com>,
	Andrea Arcangeli <aarcange@redhat.com>,
	John Stultz <john.stultz@linaro.org>,
	Pavel Emelyanov <xemul@parallels.com>,
	Cyrill Gorcunov <gorcunov@openvz.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Martin Runge <Martin.Runge@rohde-schwarz.com>,
	Andreas Brief <Andreas.Brief@rohde-schwarz.com>
Subject: Re: [PATCH] x86, vdso32: fix out of memory handling setup vDSO
Date: Thu, 20 Mar 2014 10:06:42 -0700	[thread overview]
Message-ID: <532B2022.90907@zytor.com> (raw)
In-Reply-To: <CALCETrWR-2DpSorAaQpru5u9igNXCqP66=43a+_bRs3F0q8KOA@mail.gmail.com>

On 03/20/2014 09:56 AM, Andy Lutomirski wrote:
> 
> Holy cow the 32-bit vdso code is a mess.  I have a patch to clean up
> this bit of it, and I'll send it out once I've tested it a bit.
> 

Thanks.

	-hpa



  reply	other threads:[~2014-03-20 17:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-20  7:45 [PATCH] x86, vdso32: fix out of memory handling setup vDSO Stefani Seibold
2014-03-20  9:53 ` Thomas Gleixner
2014-03-20 10:49   ` Thomas Gleixner
2014-03-20 11:38   ` Stefani Seibold
2014-03-20 12:30     ` Thomas Gleixner
2014-03-20 15:02       ` Andy Lutomirski
2014-03-20 15:15         ` Thomas Gleixner
2014-03-20 15:18           ` Andy Lutomirski
2014-03-20 15:59             ` H. Peter Anvin
2014-03-20 16:56               ` Andy Lutomirski
2014-03-20 17:06                 ` H. Peter Anvin [this message]
2014-03-20 22:01                 ` [PATCH] x86: Load the 32-bit vdso in place, just like the 64-bit vdsos Andy Lutomirski
2014-03-20 22:30                   ` [tip:x86/vdso] " tip-bot for Andy Lutomirski

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=532B2022.90907@zytor.com \
    --to=hpa@zytor.com \
    --cc=Andreas.Brief@rohde-schwarz.com \
    --cc=Martin.Runge@rohde-schwarz.com \
    --cc=aarcange@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=gorcunov@openvz.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mingo@redhat.com \
    --cc=stefani@seibold.net \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=xemul@parallels.com \
    /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.