The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Remove CONFIG_FORCE_INLINING from defconfigs
Date: Mon, 11 Feb 2008 22:53:11 +0200	[thread overview]
Message-ID: <20080211205311.GD2959@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <1202761747.10004.11.camel@brick>

On Mon, Feb 11, 2008 at 12:29:06PM -0800, Harvey Harrison wrote:
> Option has been removed as of:
> 185c045c245f46485ad8bbd8cc1100e986ff3f13 x86, core: remove CONFIG_FORCED_INLINING
>...

I'm not a fan of patching defconfig's this way - this will only bring 
tons of patch conflicts (consider what happens when anyone already has
a completely updated defconfig in his tree and your patch goes in first).

What you do manually already happens automatically when a maintainer 
updates a defconfig.

And for not regularly updated defconfigs one obsolete option more or 
less does not matter at all - even more since apart from a warning 
there's anyway no problem.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2008-02-11 20:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-11 20:29 [PATCH] Remove CONFIG_FORCE_INLINING from defconfigs Harvey Harrison
2008-02-11 20:53 ` Adrian Bunk [this message]
2008-02-11 21:05   ` Harvey Harrison

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=20080211205311.GD2959@cs181133002.pp.htv.fi \
    --to=bunk@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=harvey.harrison@gmail.com \
    --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