From: Andi Kleen <ak@suse.de>
To: Joe Korty <joe.korty@ccur.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mqueues-4.00-lib-a0.patch
Date: 20 Nov 2003 18:15:25 +0100 [thread overview]
Message-ID: <p73brr7otaq.fsf@oldwotan.suse.de> (raw)
In-Reply-To: <20031120165500.GA5569@rudolph.ccur.com.suse.lists.linux.kernel>
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.
-Andi
next parent reply other threads:[~2003-11-20 17:16 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 ` Andi Kleen [this message]
2003-11-20 18:51 ` [PATCH] mqueues-4.00-lib-a0.patch Joe Korty
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=p73brr7otaq.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=joe.korty@ccur.com \
--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 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.