From: Matt Porter <porter@cox.net>
To: Eugene Surovegin <ebs@ebshome.net>
Cc: brian.auld@adic.com, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Kernel Preemption patch
Date: Tue, 25 Feb 2003 21:18:43 -0700 [thread overview]
Message-ID: <20030225211843.B11988@home.com> (raw)
In-Reply-To: <5.1.0.14.2.20030224135756.0465b778@mail.ebshome.net>; from ebs@ebshome.net on Mon, Feb 24, 2003 at 02:29:18PM -0800
On Mon, Feb 24, 2003 at 02:29:18PM -0800, Eugene Surovegin wrote:
> I can make a patch for 2.4.19 PPC devel tree snapshot with all those
> patches and my fixes if you want.
Thanks. I placed Eugene's patch at ftp://source.mvista.com/pub/linuxppc/
There should be a pointer from penguinppc.org to this site in the
near future. Hopefully, that will make it more noticeable.
Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-02-26 4:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 20:45 Kernel Preemption patch brian.auld
2003-02-24 20:57 ` Better Real time performance Prakash kanthi
2003-02-24 22:29 ` Kernel Preemption patch Eugene Surovegin
2003-02-25 9:12 ` Stefan Roese
2003-02-25 13:24 ` Matt Porter
2003-02-26 4:18 ` Matt Porter [this message]
2003-02-26 4:25 ` Eugene Surovegin
2003-02-26 4:52 ` Matt Porter
-- strict thread matches above, loose matches on Subject: below --
2003-02-25 14:32 brian.auld
2003-02-26 4:14 ` Matt Porter
[not found] <995FF289C9D69747A09E42992644595405B23683@penguin.adic.com>
2003-02-24 21:15 ` Wolfgang Denk
2003-02-24 15:56 brian.auld
2003-02-24 18:02 ` Eugene Surovegin
2003-02-24 19:06 ` Todd Poynor
2003-02-24 15:38 brian.auld
2003-02-24 18:05 ` Eugene Surovegin
2003-02-24 18:50 ` Matt Porter
2003-02-24 12:54 brian.auld
2003-02-23 22:28 brian.auld
2003-02-23 22:33 ` Allen Curtis
2003-02-23 22:54 ` Eugene Surovegin
2003-02-23 23:05 ` Eugene Surovegin
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=20030225211843.B11988@home.com \
--to=porter@cox.net \
--cc=brian.auld@adic.com \
--cc=ebs@ebshome.net \
--cc=linuxppc-embedded@lists.linuxppc.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.