From: Vaibhav Hiremath <vaibhav.hiremath@linaro.org>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: linux-mmc <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH-v2 0/3] mmc: sdhci-pxav3: Fix tabbing issue
Date: Tue, 15 Sep 2015 19:36:11 +0530 [thread overview]
Message-ID: <55F825D3.9070501@linaro.org> (raw)
In-Reply-To: <CAPDyKFov6uADy_o944hZS9es6hkr4WM9EV1t9MXe94TcwEHuwQ@mail.gmail.com>
On Tuesday 15 September 2015 05:58 PM, Ulf Hansson wrote:
> On 7 September 2015 at 13:31, Vaibhav Hiremath
> <vaibhav.hiremath@linaro.org> wrote:
>> Trivial patch-series, which fixes the tabbing issue in the driver,
>> uses the BIT macro for bit fields and prints notice on -EPROBE_DEFER
>> in sdhci_add_host() function on regulator unavailability.
>>
>> V1 => V2
>> ========
>> - Fixed all comments from Joe, mostly alignment changes
>> - Separated BIT macro usage patch into new one.
>> - changed error to kernel notice for EPROBE_DEFER in sdhci_add_host()
>>
>> Note: This patch-series should get merged before another series -
>>
>> [PATCH-v2 0/7] mmc: sdhci-pxav3: Enable support for PXA1928 SDCHI controller
>>
>> Vaibhav Hiremath (3):
>> mmc: sdhci-pxav3: Fix tabbing issue
>> mmc: sdhci-pxav3: Use BIT macro for bit field definitions
>> mmc: sdhci: print notice on -EPROBE_DEFER in sdhci_add_host() fn
>>
>> drivers/mmc/host/sdhci-pxav3.c | 46 +++++++++++++++++++++---------------------
>> drivers/mmc/host/sdhci.c | 5 ++++-
>> 2 files changed, 27 insertions(+), 24 deletions(-)
>>
>> --
>> 1.9.1
>>
>
> Hi Vaibhav,
>
> FYI, I won't be picking up any of these patches. Primarily because I
> don't think they improves the code and other people also seems to
> agree to that.
>
> Regarding patch1 and similar patches which deals with only fixing
> checkpatch warnings/errors. In most cases I don't like such changes,
> as they makes it harder to use "git blame" when you want to find out
> which commit that introduced a change.
>
Honestly, I also agree with you.
But recently I have been told to do these changed to get my
main/feature changes accepted :)
No issues, I am OK to drop them.
These are just beautification changes and as you rightly
said it makes 'git blame' difficult to find original change commit.
Thanks,
Vaibhav
prev parent reply other threads:[~2015-09-15 14:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 11:31 [PATCH-v2 0/3] mmc: sdhci-pxav3: Fix tabbing issue Vaibhav Hiremath
2015-09-07 11:31 ` [PATCH-v2 1/3] " Vaibhav Hiremath
2015-09-07 11:56 ` Jisheng Zhang
2015-09-07 12:52 ` Vaibhav Hiremath
2015-09-07 11:31 ` [PATCH-v2 2/3] mmc: sdhci-pxav3: Use BIT macro for bit field definitions Vaibhav Hiremath
[not found] ` <1441625471-16315-1-git-send-email-vaibhav.hiremath-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-09-07 11:31 ` [PATCH-v2 3/3] mmc: sdhci: print notice on -EPROBE_DEFER in sdhci_add_host() fn Vaibhav Hiremath
2015-09-15 12:28 ` [PATCH-v2 0/3] mmc: sdhci-pxav3: Fix tabbing issue Ulf Hansson
2015-09-15 14:06 ` Vaibhav Hiremath [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=55F825D3.9070501@linaro.org \
--to=vaibhav.hiremath@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=ulf.hansson@linaro.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;
as well as URLs for NNTP newsgroup(s).