From: Jon Masters <jonathan@jonmasters.org>
To: Eugene Surovegin <ebs@ebshome.net>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: [Fwd: ppc4xx Ports]
Date: Fri, 14 Nov 2003 12:51:58 +0000 [thread overview]
Message-ID: <3FB4CFEE.3060604@jonmasters.org> (raw)
In-Reply-To: <20031114004805.GA9585@gate.ebshome.net>
Eugene Surovegin wrote:
| Could you elaborate on that? What bugs are present in current
| linuxppc-2.4? Why are you reworking PTE stuff?
As I said before I am not using linuxppc-2.4 tree so I need to fix up
the stock kernel tree.
Jon.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-11-14 12:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 23:42 [Fwd: ppc4xx Ports] Jon Masters
2003-11-13 23:44 ` Dan Kegel
2003-11-13 23:51 ` Jon Masters
2003-11-14 0:20 ` Eugene Surovegin
2003-11-14 0:36 ` Jon Masters
2003-11-14 0:48 ` Eugene Surovegin
2003-11-14 12:51 ` Jon Masters [this message]
2003-11-26 15:52 ` Peter Vandenabeele
2003-11-27 22:52 ` Jon Masters
2003-11-27 22:58 ` Jon Masters
2003-12-03 8:16 ` Peter Ryser
2003-11-28 14:16 ` Jon Masters
2003-12-03 3:05 ` The wonders of 2.4.23 [WAS: Re: [Fwd: ppc4xx Ports]] Jon Masters
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=3FB4CFEE.3060604@jonmasters.org \
--to=jonathan@jonmasters.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).