public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Jiri Kosina <jkosina@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: How to remove 2000+ lines from 400+ defconfig files?
Date: Tue, 15 Nov 2011 19:39:51 +0100	[thread overview]
Message-ID: <4EC2B1F7.6090108@suse.cz> (raw)
In-Reply-To: <1321371462.20271.201.camel@x61.thuisdomein>

Dne 15.11.2011 16:37, Paul Bolle napsal(a):
> On Tue, 2011-11-15 at 14:14 +0100, Jiri Kosina wrote:
>> I am fine taking those through trivial.git and handling the fallout.
>
> Great.
>
>> The only ones I'd have objections to taking immediately are those which are
>> actually still referenced somewhere in the code.
>> For those, either taking them through appropriate maintainers, or having
>> their Acked-by would be required.
>
> I don't mind. That shouldn't be a lot of extra work for me.
>
> But, I do have a naive question: are defconfigs meant to be drop in
> replacements for .config files or is one supposed to first feed them to
> the config tools to generate an up to date .config?

defconfig files are used as input of the conf program.

  Since, if one is
> supposed to feed them to the config tools first it doesn't matter
> whether the (outdated) macros are still used somewhere in the code,
> doesn't it? The config tools will simply drop all macros they can't
> match with Kconfig symbols. (Or don't they? Michal?)

Yes, they will not appear in the .config.

Michal

  reply	other threads:[~2011-11-15 18:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1321362602.20271.192.camel@x61.thuisdomein>
2011-11-15 13:14 ` How to remove 2000+ lines from 400+ defconfig files? Jiri Kosina
2011-11-15 15:37   ` Paul Bolle
2011-11-15 18:39     ` Michal Marek [this message]
2011-11-15 18:57       ` Dave Jones
2011-11-15 19:21         ` Paul Bolle
2011-11-15 19:26       ` Paul Bolle
2011-11-15 20:54         ` Michal Marek

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=4EC2B1F7.6090108@suse.cz \
    --to=mmarek@suse.cz \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    /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