From: Anders Kaseorg <andersk@ksplice.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86, vdso: SHN_LORESERVE is an inclusive lower bound
Date: Mon, 25 Apr 2011 19:18:18 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1104251850430.26664@dr-wily.mit.edu> (raw)
In-Reply-To: <4DB5F17C.8040105@goop.org>
On Mon, 25 Apr 2011, Jeremy Fitzhardinge wrote:
> On 04/25/2011 07:28 AM, Anders Kaseorg wrote:
> > Test for >= SHN_LORESERVE instead of > SHN_LORESERVE.
>
> Yep, seems reasonable. Did this cause a problem, or is it just
> something you noticed?
I just noticed it (while writing “modpost: Update 64k section support for
binutils 2.18.50”: http://thread.gmane.org/gmane.linux.kernel/1130613 ).
Anders
prev parent reply other threads:[~2011-04-25 23:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 14:28 Anders Kaseorg
2011-04-25 22:11 ` Jeremy Fitzhardinge
2011-04-25 23:18 ` Anders Kaseorg [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=alpine.DEB.2.02.1104251850430.26664@dr-wily.mit.edu \
--to=andersk@ksplice.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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
all inboxes | Powered by JetHome®