From: Christoph Hellwig <hch@ns.caldera.de>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org, linux-kbuild@torque.net
Subject: Re: [KBUILD] Re: PATCH - kbuild documentation.
Date: Thu, 30 Nov 2000 09:40:30 +0100 [thread overview]
Message-ID: <20001130094030.A18717@caldera.de> (raw)
In-Reply-To: <14885.37565.611695.816426@notabene.cse.unsw.edu.au> <200011300036.eAU0aTc05028@flint.arm.linux.org.uk>
In-Reply-To: <200011300036.eAU0aTc05028@flint.arm.linux.org.uk>; from rmk@arm.linux.org.uk on Thu, Nov 30, 2000 at 12:36:28AM +0000
On Thu, Nov 30, 2000 at 12:36:28AM +0000, Russell King wrote:
> and CONFIG_FOO=y and CONFIG_BAR=m? What about CONFIG_FOO=y and
> CONFIG_BAR=y? Do we still support this method? If not, what is the
> recommended way of doing this sort of stuff?
To do this you need to extend the scheme a little bit. I once wrote a
patch that implements this scheme in a common place -
$(TOPDIR)/Makefile.inc - and sent it to Linux for inclusion, but it was
not applied. IF you are interested I could try to search it...
Christoph
--
Always remember that you are unique. Just like everyone else.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-30 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-29 23:35 Neil Brown
2000-11-30 0:36 ` Russell King
2000-11-30 8:40 ` Christoph Hellwig [this message]
2000-11-30 9:49 ` Neil Brown
2000-11-30 11:46 ` [KBUILD] " Peter Samuelson
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=20001130094030.A18717@caldera.de \
--to=hch@ns.caldera.de \
--cc=linux-kbuild@torque.net \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=rmk@arm.linux.org.uk \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®