From: Ira K Weiny <iweiny@falcon.csc.calpoly.edu>
To: linuxppc-dev@lists.linuxppc.org (linuxdev)
Subject: kernel sources
Date: Tue, 14 Sep 1999 14:11:40 -0700 (PDT) [thread overview]
Message-ID: <199909142111.OAA26938@falcon.csc.calpoly.edu> (raw)
Where is the proper place to get the kernel source?
I have both 2.2.12 and 2.3.16 from kernel.org but neither seem to be in sync
with the other developers on this list. (I had to hand patch the PCI changes
submitted. And the 2.3.16 will not even build due to a missing header?)
I know 2.3.16 is a development snapshot and I can't complain about that. I
have seen many posts for the "vger" trees and the only web/ftp site I have
found was for Sparc and only has 2.1 version kernels?
What am I missing?
Ira Weiny
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~1999-09-14 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-14 21:11 Ira K Weiny [this message]
1999-09-15 5:10 ` kernel sources Martin Costabel
[not found] <374E4267.5BF46F98@wanadoo.fr>
1999-05-30 12:21 ` Problem compiling egcs Martin Costabel
1999-05-31 14:19 ` Kernel sources Jerry Quinn
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=199909142111.OAA26938@falcon.csc.calpoly.edu \
--to=iweiny@falcon.csc.calpoly.edu \
--cc=linuxppc-dev@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).