From: Grant Likely <glikely@gmail.com>
To: linuxppc-embedded@ozlabs.org, Sylvain Munaut <tnt@246tnt.com>
Subject: Status of linux-2.5-mpc52xx tree
Date: Fri, 22 Apr 2005 11:18:55 -0600 [thread overview]
Message-ID: <528646bc050422101815562d6c@mail.gmail.com> (raw)
Sylvain, I'm wondering what the status is of the linux-2.5-mpc52xx
tree that you're maintaining. Specifically, what patches have not yet
been merged into Linus' tree? Also, with the whole BK debacle, have
you given any thought to what you are going to transition to?
BTW, thank you very much for the mpc52xx work that you've assembled.=20
It's been a huge boost for my work.
Finally, can anybody point me to (or send me) a snapshot (or diff from
mainline) of the linux-2.5-mpc52xx tree? Due to corporate firewall
issues I cannot use bitkeeper. As far as I can tell it looks like the
FEC driver has not been merged upstream yet.
Thanks,
g.
next reply other threads:[~2005-04-22 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-22 17:18 Grant Likely [this message]
2005-04-24 18:12 ` Status of linux-2.5-mpc52xx tree Sylvain Munaut
-- strict thread matches above, loose matches on Subject: below --
2005-04-25 3:46 Sam Song
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=528646bc050422101815562d6c@mail.gmail.com \
--to=glikely@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=tnt@246tnt.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).