From: Dan Malek <dan@netx4.com>
To: Shuangjun Zhu <r44089@email.sps.mot.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: memory map
Date: Mon, 24 Apr 2000 12:09:18 -0400 [thread overview]
Message-ID: <390471AE.60EB1394@embeddededge.com> (raw)
In-Reply-To: 006401bfadab$80c796c0$69f001dc@sjzhu.sps.mot.com
Shuangjun Zhu wrote:
> Where can I get the code?
Same place as everything else. It is currently in the fsmlabs BitKeeper
tree, and when Cort merges with Linus it will find its way to kernel.org.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-04-24 16:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-24 5:11 memory map Shuangjun Zhu
2000-04-24 16:09 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-27 19:04 Memory map Konstantin Sabodash
2000-11-27 19:22 ` Dan Malek
2000-04-25 9:31 Re:Re: memory map zzh
2000-04-25 17:05 ` Dan Malek
2000-04-24 3:24 zzh
2000-04-24 3:54 ` Dan Malek
2000-04-23 22:16 ` Steve Tarr
2000-04-24 16:07 ` Dan Malek
2000-04-21 9:49 zzh
2000-04-21 16:58 ` Dan Malek
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=390471AE.60EB1394@embeddededge.com \
--to=dan@netx4.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=r44089@email.sps.mot.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).