From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: Switch apm to unlocked_kernel
Date: Fri, 23 May 2008 10:25:37 -0700 [thread overview]
Message-ID: <20080523102537.2fbc74f3.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080523232339.27a28b5b.sfr@canb.auug.org.au>
On Fri, 23 May 2008 23:23:39 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Alan,
>
> On Fri, 23 May 2008 12:06:17 +0100 Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> >
> > Andrew shouts at me if I send him patches that don't fix the style of
> > the lines around so you get some style changes even when I cut bits out
> > of diffs.
Don't think so. Unrelated changes are well-known poor-form.
I do think that if one is already changing a line which is incorrectly
laid out then there's no point in _leaving_ it incorrect. There's no
downside to fixing it.
That being said, it's often sorely tempting to go hunting down nearby
sillinesses. I succumb to that temptation and usually won't complain
when others do also, up to a point.
> I think that approach is *stupid* too and style should be done
> > after for the entire file.
>
> Then let the maintainer (nominally me) shout at Andrew. I don't agree
> with those style changes and we usually leave such purely stylistic
> things to the maintainer of the file in question.
mm, not really. Wrong is wrong and if nominal maintainer insists on
retaining wrong we have cheery bunfights about it.
> If Andrew requires
> these changes, then Andrew is wrong about this. It just confuses the
> real changes and adds to the overheads of those trying to do reviews (of
> which we have too few).
I think those changes went above and beyond the call.
> And in this case "fix" is in the eye of the
> beholder.
And that is why we have a standard - so that different parts of the
kernel do not end up having different appearance due to local
preferences.
next prev parent reply other threads:[~2008-05-23 17:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 20:22 [PATCH] x86: Switch apm to unlocked_kernel Alan Cox
2008-05-23 1:03 ` Stephen Rothwell
2008-05-23 11:06 ` Alan Cox
2008-05-23 13:23 ` Stephen Rothwell
2008-05-23 17:25 ` Andrew Morton [this message]
2008-05-23 11:36 ` Kevin Winchester
2008-05-24 18:59 ` [RFC] " Kevin Winchester
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=20080523102537.2fbc74f3.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sfr@canb.auug.org.au \
/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.