From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Chihau Chau <chihau@gmail.com>
Cc: rjw@sisk.pl, kaneshige.kenji@jp.fujitsu.com, yu.zhao@intel.com,
bjorn.helgaas@hp.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, Chihau Chau <chihau@gmail.com>
Subject: Re: [PATCH] Drivers: pci: code style cleanup
Date: Fri, 12 Mar 2010 17:27:38 -0800 [thread overview]
Message-ID: <20100312172738.522f435f@jbarnes-piketon> (raw)
In-Reply-To: <1268329983-2603-1-git-send-email-chihau@gmail.com>
On Thu, 11 Mar 2010 14:53:03 -0300
Chihau Chau <chihau@gmail.com> wrote:
> From: Chihau Chau <chihau@gmail.com>
>
> This is a code style cleanup related with spaces, like a lot of trailing
> withspaces, spaces before a TAB, to use "foo * bar" instead of "foo *bar"
> and to put a else sentence below close brace '}'.
>
> Signed-off-by: Chihau Chau <chihau@gmail.com>
Unless you're doing some other work in this area and include this patch
in a larger patchset, I'm inclined to reject it, since it just creates
churn for others for no good reason.
In other words, if developer A is making real changes in these areas
that would invalidate developer B's patches, that's fine. But I don't
think it's ok to let cleanup patches invalidate developer B's work.
Hope that's clear. Don't get me wrong, I like the fact that in Linux
we're not afraid to clean stuff up. I just don't like it getting in
the way of real work.
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2010-03-13 1:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 17:53 Chihau Chau
2010-03-13 1:27 ` Jesse Barnes [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=20100312172738.522f435f@jbarnes-piketon \
--to=jbarnes@virtuousgeek.org \
--cc=bjorn.helgaas@hp.com \
--cc=chihau@gmail.com \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=yu.zhao@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
all inboxes | Powered by JetHome®