From: Andi Kleen <ak@suse.de>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Adrian Bunk <bunk@stusta.de>, Dave Jones <davej@redhat.com>,
Ulrich Drepper <drepper@redhat.com>,
linux-stable <stable@kernel.org>
Subject: Re: [stable][patch] x86_64: fix number of ia32 syscalls
Date: Tue, 23 May 2006 01:11:17 +0200 [thread overview]
Message-ID: <200605230111.18121.ak@suse.de> (raw)
In-Reply-To: <200605221701_MC3-1-C081-B4B3@compuserve.com>
On Monday 22 May 2006 22:59, Chuck Ebbert wrote:
> Recent discussions about whether to print a message about unimplemented
> ia32 syscalls on x86_64 have missed the real bug: the number of ia32
> syscalls is wrong in 2.6.16. Fixing that kills the message.
There is already a slightly different patch for this in the FF tree.
-Andi
next prev parent reply other threads:[~2006-05-22 23:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 20:59 [stable][patch] x86_64: fix number of ia32 syscalls Chuck Ebbert
2006-05-22 23:11 ` Andi Kleen [this message]
2006-05-22 23:24 ` Chris Wright
2006-05-22 23:31 ` Brian Gerst
2006-05-23 2:50 ` Andi Kleen
2006-05-23 14:33 ` Michael Buesch
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=200605230111.18121.ak@suse.de \
--to=ak@suse.de \
--cc=76306.1226@compuserve.com \
--cc=bunk@stusta.de \
--cc=davej@redhat.com \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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.