From: Tejun Heo <tj@kernel.org>
To: paulmcquad <paulmcquad@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH] Subject: ata: libata Fixed Coding style & tabs
Date: Sat, 29 Mar 2014 09:10:42 -0400 [thread overview]
Message-ID: <20140329131042.GA5553@htj.dyndns.org> (raw)
In-Reply-To: <5335B9BA.3070408@gmail.com>
Hello, Paul.
On Fri, Mar 28, 2014 at 06:04:42PM +0000, paulmcquad wrote:
> From 718d05b6aae57da1a990e38b99a4e3d880717d77 Mon Sep 17 00:00:00 2001
> From: Paul McQuade <paulmcquad@gmail.com>
> Date: Fri, 28 Mar 2014 17:58:02 +0000
> Subject: [PATCH] Subject: ata: libata Fixed Coding style & tabs
>
> Made files below checkpatch.pl clean.
I don't think I'm gonna apply the patch. This type of mass whitespace
cleanups tend to cause conflicts without making anything substantially
better. I'd much prefer to localized style cleanups when code
close-by is being changed. Big ones are fine if they're accompanied
by large actual changes too.
Thanks.
--
tejun
prev parent reply other threads:[~2014-03-29 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 18:04 [PATCH] Subject: ata: libata Fixed Coding style & tabs paulmcquad
2014-03-29 13:10 ` Tejun Heo [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=20140329131042.GA5553@htj.dyndns.org \
--to=tj@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmcquad@gmail.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