linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@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>
Subject: Re: [PATCH v2 1/7] pinctrl: UniPhier: add UniPhier pinctrl core support
Date: Sun, 19 Jul 2015 13:19:43 +0900	[thread overview]
Message-ID: <CAK7LNARjFdM6du3tM7RfdXEHktM=4z6XrYag9DM-z+Y0o79jNA@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdZFfypZfDAmULcC1_q_bYD-nsh2H0rMAqo+ncWsBx6m=A@mail.gmail.com>

Hi Linus,



2015-07-16 16:20 GMT+09:00 Linus Walleij <linus.walleij@linaro.org>:
> On Tue, Jul 14, 2015 at 4:40 AM, Masahiro Yamada
> <yamada.masahiro@socionext.com> wrote:
>
>> The core support for the pinctrl drivers for all the UniPhier SoCs.
>>
>> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
>> ---
>>
>> Changes in v2:
>>   - drop vogus THIS_MODULE because this file is always built-in
>>   - drop vogus "include <linux/module.h> because this file is
>>     always built-in
>
> This looks nice and uses all generic facilities we have.
>
> Patch applied.
>
> Yours,
> Linus Walleij
>



I saw the applied patch and noticed "Changes in v2"
was moved to git-description.


commit 6e908892025885b07e804dc6c05aab6ce1e06832
Author: Masahiro Yamada <yamada.masahiro@socionext.com>
Date:   Tue Jul 14 11:40:01 2015 +0900

    pinctrl: UniPhier: add UniPhier pinctrl core support

    The core support for the pinctrl drivers for all the UniPhier SoCs.

    Changes in v2:
      - drop vogus THIS_MODULE because this file is always built-in
      - drop vogus "include <linux/module.h> because this file is
        always built-in

    Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>




Do we need to record such stuff in the git history?

In my opinion, the difference between patch versions
should be mentioned to help reviewers, but not included in the git repository.

Early versions are often so immature that they must be improved
in the review process.
No point to record what was updated from those versions, I think.

This is why I put "changed in v2" below the "---".



-- 
Best Regards
Masahiro Yamada

  reply	other threads:[~2015-07-19  4:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-14  2:40 [PATCH v2 0/7] This series adds pinctrl drivers for UniPhier SoC family Masahiro Yamada
2015-07-14  2:40 ` [PATCH v2 1/7] pinctrl: UniPhier: add UniPhier pinctrl core support Masahiro Yamada
2015-07-16  7:20   ` Linus Walleij
2015-07-19  4:19     ` Masahiro Yamada [this message]
2015-07-20  9:18       ` Linus Walleij
2015-07-14  2:40 ` [PATCH v2 2/7] pinctrl: UniPhier: add UniPhier PH1-LD4 pinctrl driver Masahiro Yamada
2015-07-16  7:22   ` Linus Walleij
2015-07-14  2:40 ` [PATCH v2 3/7] pinctrl: UniPhier: add UniPhier PH1-Pro4 " Masahiro Yamada
2015-07-16  7:28   ` Linus Walleij
2015-07-14  2:40 ` [PATCH v2 4/7] pinctrl: UniPhier: add UniPhier PH1-sLD8 " Masahiro Yamada
2015-07-16  7:29   ` Linus Walleij
2015-07-14  2:40 ` [PATCH v2 5/7] pinctrl: UniPhier: add UniPhier PH1-Pro5 " Masahiro Yamada
2015-07-16  7:31   ` Linus Walleij
2015-07-14  2:40 ` [PATCH v2 6/7] pinctrl: UniPhier: add UniPhier ProXstream2 " Masahiro Yamada
2015-07-16  7:33   ` Linus Walleij
2015-07-14  2:40 ` [PATCH v2 7/7] pinctrl: UniPhier: add UniPhier PH1-LD6b " Masahiro Yamada
2015-07-16  7:36   ` Linus Walleij

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='CAK7LNARjFdM6du3tM7RfdXEHktM=4z6XrYag9DM-z+Y0o79jNA@mail.gmail.com' \
    --to=yamada.masahiro@socionext.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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).