From: Tom Rini <trini@kernel.crashing.org>
To: Alan Cox <alan@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.20-rc1-ac2
Date: Thu, 14 Nov 2002 10:31:52 -0700 [thread overview]
Message-ID: <20021114173152.GA605@opus.bloom.county> (raw)
In-Reply-To: <200211141622.gAEGMhX17361@devserv.devel.redhat.com>
On Thu, Nov 14, 2002 at 11:22:43AM -0500, Alan Cox wrote:
>
> [+ indicates stuff that went to Marcelo, o stuff that has not,
> * indicates stuff that is merged in mainstream now, X stuff that proved
> bad and was dropped out, - indicates stuff not relevant to the main tree]
>
> Linux 2.4.20-rc1-ac2
> o Ptrace NT flag fix (Andrea Arcangeli)
> o lcall NT clear fixes (Petr Vandrovec)
Is the patch from Andrea needed in addition to Petr's patch? If I
followed the thread right it looks like Andrea later said that it wasn't
needed (and I've locally tested both test cases with just Petr's patch
with nothing bad seeming to happen).
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
prev parent reply other threads:[~2002-11-14 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 16:22 Linux 2.4.20-rc1-ac2 Alan Cox
2002-11-14 16:44 ` Danny ter Haar
2002-11-14 19:13 ` David Dyck
2002-11-14 17:31 ` Tom Rini [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=20021114173152.GA605@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=alan@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox