public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: kbuild-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Have split-include take another argument
Date: Thu, 14 Nov 2002 16:17:21 -0700	[thread overview]
Message-ID: <20021114231721.GB608@opus.bloom.county> (raw)
In-Reply-To: <Pine.LNX.4.33.0211120917060.4022-100000@localhost.localdomain>

On Thu, Nov 14, 2002 at 03:01:18PM -0600, Kai Germaschewski wrote:
> On Mon, 11 Nov 2002, Tom Rini wrote:
> 
> > Hello.  The following patch makes split-include take another argument,
> > which is the prefix of what is being split up.  This is needed since I'm
> > working on a system which will allow for various params in the kernel to
> > be tweaked at compile-time, without offering numerous CONFIG options
> > (see http://marc.theaimsgroup.com/?l=linux-kernel&m=103669658505842&w=2).
> > I'm sending this out for two reasons.  First, does anyone see any
> > problems with the patch itself?  Second, Kai, would you be willing to
> > apply this patch now, or would should I wait until the system is ready?
> 
> Hmmh, I think I'd rather like to wait for the rest of the patch to see 
> what its actual purpose is. If at all possible, I'd like to avoid 
> introducing further hacks like this into kbuild, but that's more easily 
> discussed when I can see what you're trying to achieve.

Okay.  I hope to have another version of the patch out soon, and with a
few more kbuild questions once I convince myself that most of it works
(Adding in something similar to the CONFIG tweaking done by fixdep, but
with no real convinient way to see if the user changed something or
not).

-- 
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

      reply	other threads:[~2002-11-14 23:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-11 17:06 [PATCH] Have split-include take another argument Tom Rini
2002-11-11 23:37 ` Peter Samuelson
2002-11-12 15:09   ` Tom Rini
2002-11-14 21:01 ` Kai Germaschewski
2002-11-14 23:17   ` Tom Rini [this message]

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=20021114231721.GB608@opus.bloom.county \
    --to=trini@kernel.crashing.org \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --cc=kbuild-devel@lists.sourceforge.net \
    --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