All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bryce Harrington <bryce@osdl.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [PATCH] Fix for some typos in Documentation/makefiles.txt
Date: Wed, 20 Sep 2006 22:05:58 +0000	[thread overview]
Message-ID: <20060920220558.GF17157@osdl.org> (raw)
In-Reply-To: <20060920194337.GD17157@osdl.org>

On Wed, Sep 20, 2006 at 11:10:25PM +0200, Sam Ravnborg wrote:
> On Wed, Sep 20, 2006 at 12:43:37PM -0700, Bryce Harrington wrote:
> > Hi Kai,
> > 
> > I noticed a few typos while reading makefiles.txt to learn about the
> > kbuild system.  Attached is a patch against 2.6.18 to fix them.
> 
> Thanks Bryce.
> 
> I will apply is as soon as I get the kbuild.git tree in proper shape
> for 2.6.19.
> 
> 	Sam

Great, thanks.  If you don't mind, I also have a question about kbuild...

For automated kernel testing when we wish to customize a config, such as
iterating through memory models, tuning settings, experimental features,
etc. we can do this through simple substitutions.

However, this doesn't handle dependencies, such as if choice of a given
memory model should alter other config settings.

Do you know of a tool or technique which can be used from the
commandline to alter an arbitrary symbol's value in a given .config
file, and cascade the change to any dependent symbols, using a given
kernel Kconfig?

From what I have gathered, there is no such thing that does exactly
this; do you know if this is true?

Bryce


_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors

  parent reply	other threads:[~2006-09-20 22:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-20 19:43 [KJ] [PATCH] Fix for some typos in Documentation/makefiles.txt Bryce Harrington
2006-09-20 21:10 ` Sam Ravnborg
2006-09-20 22:05 ` Bryce Harrington [this message]
2006-09-20 23:41 ` Sam Ravnborg
2006-09-24  8:43 ` Sam Ravnborg
2006-09-25  6:50 ` Bryce Harrington

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=20060920220558.GF17157@osdl.org \
    --to=bryce@osdl.org \
    --cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.