From: Matthew Locke <mlocke@mvista.com>
To: Subodh Nijsure <subodh@best.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Status of linux-ppc kernel.
Date: Thu, 22 Feb 2001 11:56:41 -0800 [thread overview]
Message-ID: <3A956EF9.E532F518@mvista.com> (raw)
In-Reply-To: 200102221739.JAA03312@shell9.ba.best.com
Subodh Nijsure wrote:
>
> Also there seem to be few patches like Wolfgang's ethernet patch
> found on ftp.denx.de or m8xx_pcmcia stuff that hasn't shown up in
> 2.4.X latest kernel. Are these things going to get merged into
> "mainline" sometime and does anybody know probable dates etc.?
m8xx_pcmcia is a part of the pcmcia-cs tree. The kernel changes depend
on where you ioremap memory for pcmcia, which is board dependent. I
need to send Dan a kernel patch for the EP boards, but I haven't done it
yet:(
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-02-22 19:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-22 17:39 Status of linux-ppc kernel Subodh Nijsure
2001-02-22 19:56 ` Matthew Locke [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=3A956EF9.E532F518@mvista.com \
--to=mlocke@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=subodh@best.com \
/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).