public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PATCH 2.4.4.3: 3rdparty driver support for kbuild
Date: Tue, 24 Apr 2001 08:57:36 +1000	[thread overview]
Message-ID: <12679.988066656@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Sun, 15 Apr 2001 05:25:24 EDT." <3AD96904.9274E46C@mandrakesoft.com>

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.

    As for (2) you have a separate object directory for each set of
    config options.  But instead of manually building a single source
    tree from various patches, the patch sets are kept separate and
    kbuild 2.5 logically constructs a single kernel source tree from
    the various source trees.  This is called a shadow tree system
    because the patch sets shadow the main kernel source tree.

[1] http://sourceforge.net/projects/kbuild



  reply	other threads:[~2001-04-23 22:59 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 [this message]
2001-04-23 23:03   ` Jeff Garzik
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=12679.988066656@ocs3.ocs-net \
    --to=kaos@ocs.com.au \
    --cc=jgarzik@mandrakesoft.com \
    --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