linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Adrian Bunk <bunk@stusta.de>
Cc: tony.luck@intel.com, linux-ia64@vger.kernel.org,
	grundler@parisc-linux.org, matthew@wil.cx,
	linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
	lethal@linux-sh.org, linux-mtd@lists.infradead.org,
	dwmw2@infradead.org, kkojima@rr.iij4u.or.jp,
	parisc-linux@parisc-linux.org
Subject: Re: [2.6 patch] don't allow users to set CONFIG_BROKEN=y
Date: Tue, 13 Dec 2005 22:01:57 +0000	[thread overview]
Message-ID: <20051213220157.GD24094@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20051213201920.GT23349@stusta.de>

On Tue, Dec 13, 2005 at 09:19:20PM +0100, Adrian Bunk wrote:
> On Tue, Dec 13, 2005 at 08:01:06PM +0000, Russell King wrote:
> > That means that the original review was _worthless_.  It wasn't a
> > review at all.
> > 
> > So, what I am trying to get across is the need to show the _full_ set
> > of changes to a default configuratoin when you disable CONFIG_BROKEN,
> > which is trivially producable if you run the script I've already posted.
> > 
> > You can even use that in conjunction with your present patch to produce
> > a patch which shows _exactly_ _everything_ which changes as a result of
> > disabling CONFIG_BROKEN.  Surely giving reviewers the _full_ story is
> > far better than half a story, and should be something that any change
> > to the kernel strives for.
> > 
> > If not, what's the point of the original change?
> 
> The point is that I haven't yet heard any good reason for 
> CONFIG_BROKEN=y in a defconfig.

I'm sorry, I feel like I'm beating my head against a brick wall.  I
have said everything that needs to be said, and made my position on
this patch crystal clear.

The patch to the ARM configuration files is nacked as it stands.
Please go back and rework it along the guidelines I've pointed out
several times in this thread and maybe then it becomes acceptable.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2005-12-13 22:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-11 18:52 [2.6 patch] defconfig's shouldn't set CONFIG_BROKEN=y Adrian Bunk
2005-12-11 19:21 ` Russell King
2005-12-11 19:31   ` Adrian Bunk
2005-12-11 19:44     ` Russell King
2005-12-13  0:10       ` Adrian Bunk
2005-12-13 13:34         ` Simon Richter
2005-12-13 14:00           ` Adrian Bunk
2005-12-13 17:31             ` Russell King
2005-12-13 18:05               ` [2.6 patch] don't allow users to " Adrian Bunk
2005-12-13 18:28                 ` Geert Uytterhoeven
2005-12-13 18:51                   ` Adrian Bunk
2005-12-13 18:59                   ` Jesper Juhl
2005-12-13 20:01                 ` Russell King
2005-12-13 20:19                   ` Adrian Bunk
2005-12-13 22:01                     ` Russell King [this message]
2005-12-12  9:38     ` [2.6 patch] defconfig's shouldn't " David Woodhouse

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=20051213220157.GD24094@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=bunk@stusta.de \
    --cc=dwmw2@infradead.org \
    --cc=grundler@parisc-linux.org \
    --cc=kkojima@rr.iij4u.or.jp \
    --cc=lethal@linux-sh.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=matthew@wil.cx \
    --cc=parisc-linux@parisc-linux.org \
    --cc=tony.luck@intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).