mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Clifford Wolf <clifford@clifford.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add 'make no2modconfig' config generation target
Date: Sun, 1 Jun 2008 19:42:55 +0200	[thread overview]
Message-ID: <20080601174255.GA22244@uranus.ravnborg.org> (raw)
In-Reply-To: <20080601163439.GI1369@clifford.at>

On Sun, Jun 01, 2008 at 06:34:39PM +0200, Clifford Wolf wrote:
> Hi,
> 
> On Sat, May 31, 2008 at 10:30:34AM +0200, Sam Ravnborg wrote:
> > On Sat, May 31, 2008 at 09:05:07AM +0200, Clifford Wolf wrote:
> > > The new 'make no2modconfig' make target creates a new kernel
> > > config based on the current one, switching all tristate options
> > > from 'n' to 'm'.
> > 
> > In what situations do we need this functionality?
> 
> I'm using this patch (respectively its predecessors) since many years in
> ROCK Linux to auto-generate our general purpose kernel configurations, by
> copying the default kernel config, forcing some variables to yes or no and
> then setting all tristate options which are on 'n' to 'm' using this patch.
> 
> the only alternative would be to manually check the kernel configurtion for
> each new kernel and setting all new tristate options to 'm' by hand. what a
> waste of energy that would have been for the last couple of years..  ;-)

I have a set of patched in works that will allow this in
a more general way.
It allows you to specify a base config when you do allmodconfig.
Syntax is:

   make K=rock-config allmodconfig

This will result in exactly what you want.

I will try to find time during next week to polish them and submit them
for 2nd review.

	Sam

      reply	other threads:[~2008-06-01 17:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-31  7:05 Clifford Wolf
2008-05-31  8:30 ` Sam Ravnborg
2008-06-01 16:34   ` Clifford Wolf
2008-06-01 17:42     ` Sam Ravnborg [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=20080601174255.GA22244@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=clifford@clifford.at \
    --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

all inboxes | Powered by JetHome®