From: Joe Korty <joe.korty@ccur.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mqueues-4.00-lib-a0.patch
Date: Thu, 20 Nov 2003 13:51:50 -0500 [thread overview]
Message-ID: <20031120185149.GA5735@rudolph.ccur.com> (raw)
In-Reply-To: <p73brr7otaq.fsf@oldwotan.suse.de>
On Thu, Nov 20, 2003 at 06:15:25PM +0100, Andi Kleen wrote:
> Joe Korty <joe.korty@ccur.com> writes:
> > +#ifndef __NR_mq_open
> >
> > +#ifdef __i386__
> > #define __NR_mq_open 274
> > +#elif __x86_64__
> > +#define __NR_mq_open 237
> > +#else
>
> FYI. I already allocated 237 for something else on x86-64. The patch
> is guaranteed to get broken.
Define an offical set for Opteron and I'll use it.
Joe
next prev parent reply other threads:[~2003-11-20 18:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031120165500.GA5569@rudolph.ccur.com.suse.lists.linux.kernel>
2003-11-20 17:15 ` [PATCH] mqueues-4.00-lib-a0.patch Andi Kleen
2003-11-20 18:51 ` Joe Korty [this message]
2003-11-20 16:55 Joe Korty
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=20031120185149.GA5735@rudolph.ccur.com \
--to=joe.korty@ccur.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.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