From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PATCH 2.4.4.3: 3rdparty driver support for kbuild
Date: Mon, 23 Apr 2001 19:03:45 -0400 [thread overview]
Message-ID: <3AE4B4D1.A4A17FD6@mandrakesoft.com> (raw)
In-Reply-To: <12679.988066656@ocs3.ocs-net>
Keith Owens wrote:
> On Sun, 15 Apr 2001 05:25:24 -0400,
> Jeff Garzik <jgarzik@mandrakesoft.com> wrote:
> >The attached patch, against kernel 2.4.4-pre3, adds a feature I call
> >"3rd-party support."
>
> Already covered by my 2.5 makefile rewrite[1] which has explicit
> support for third party kernel source. Shadow trees are designed
> specifically to handle this problem. I don't see the point of adding a
> script which will only be used in 2.4, especially when the vendors
> would have to change their tarball format for 2.5 formats.
>
> (3) The kernel is constructed from multiple source trees and built in a
> separate object tree.
I don't see how multiple source trees can be merged automatically with
100% accuracy.
What happens when you build with linus-tree, xfs-tree, and
reiserfs-tree, and both XFS and reiserfs touch struct file_operations,
in conflicting ways? It takes human intervention to figure that stuff
out and resolve such conflicts.
If you support multiple source trees -> single build tree, it sounds
like are you trying to integrate cvs/diff/similar into the kernel build
system, which is whacky...
Jeff
--
Jeff Garzik | The difference between America and England is that
Building 1024 | the English think 100 miles is a long distance and
MandrakeSoft | the Americans think 100 years is a long time.
| (random fortune)
next prev parent reply other threads:[~2001-04-23 23:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-15 9:25 PATCH 2.4.4.3: 3rdparty driver support for kbuild Jeff Garzik
2001-04-23 22:57 ` Keith Owens
2001-04-23 23:03 ` Jeff Garzik [this message]
2001-04-23 23:10 ` Keith Owens
2001-04-23 23:47 ` Jonathan Lundell
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=3AE4B4D1.A4A17FD6@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.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