The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: mikpe@csd.uu.se
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][2.4.21-pre6] update x86_64 for kernel_thread change
Date: Wed, 2 Apr 2003 21:48:37 +0200	[thread overview]
Message-ID: <16011.16021.699436.97176@gargle.gargle.HOWL> (raw)
In-Reply-To: <1049311995.10050.47.camel@averell>

Andi Kleen writes:
 > On Wed, 2003-04-02 at 21:18, Mikael Pettersson wrote:
 > > Building an x86_64 kernel from 2.4.21-pre6 results in two linkage
 > > errors due to the recent kernel_thread to arch_kernel_thread name change.
 > > This patch updates x86_64 for that change.
 > 
 > You need more changes to fix the ptrace hole completely.

More generic fixes or more x86_64-specific fixes?

/Mikael

  reply	other threads:[~2003-04-02 19:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-02 19:18 [PATCH][2.4.21-pre6] update x86_64 for kernel_thread change Mikael Pettersson
2003-04-02 19:33 ` Andi Kleen
2003-04-02 19:48   ` mikpe [this message]
2003-04-02 20:00     ` Andi Kleen

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=16011.16021.699436.97176@gargle.gargle.HOWL \
    --to=mikpe@csd.uu.se \
    --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