public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: "Adam J. Richter" <adam@yggdrasil.com>, linux-kernel@vger.kernel.org
Subject: Re: Replacement for "make SUBDIRS=...." in 2.5.63?
Date: 28 Feb 2003 16:05:58 +0000	[thread overview]
Message-ID: <1046448358.12902.45.camel@passion.cambridge.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0302251039080.13501-100000@chaos.physics.uiowa.edu>

On Tue, 2003-02-25 at 17:04, Kai Germaschewski wrote:

> > 	What is the proper way to rebuild just one subdirectory?  How
> > about for building externally provided modules? 
> 
> The proper way is "make vmlinux/modules". If you are sure that nothing 
> changed outside of that directory, make SUBDIRS=... is fine, but since 
> kbuild cannot know that nothing else changed (you just prohibited checking 
> the other dirs), it'll give the warning.

In the case where you're building external modules, this is just fine --
generally you're doing this on purpose. How about disabling the warning
if every element of $(SUBDIRS) starts with a '/'?

> I hope that clarifies things a bit. As I wrote earlier, I'll come up with 
> a proper and simple way to build external modules once I find the time.

If you deprecate 'make SUBDIRS=/my/module/source modules' then please
make sure whatever replacement you come up with also works with 2.0, 2.2
and 2.4 kernels, to avoid gratuitous pain for driver maintainers. :)

-- 
dwmw2


  parent reply	other threads:[~2003-02-28 15:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-25  6:33 Replacement for "make SUBDIRS=...." in 2.5.63? Adam J. Richter
2003-02-25 17:04 ` Kai Germaschewski
2003-02-28 12:48   ` Gerd Knorr
2003-02-28 16:05   ` David Woodhouse [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-25 19:26 Adam J. Richter

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=1046448358.12902.45.camel@passion.cambridge.redhat.com \
    --to=dwmw2@infradead.org \
    --cc=adam@yggdrasil.com \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --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