From: Guenter Roeck <linux@roeck-us.net>
To: Iker Perez <iker.perez@codethink.co.uk>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Version Log
Date: Tue, 30 Apr 2019 09:56:39 -0700 [thread overview]
Message-ID: <20190430165639.GB2699@roeck-us.net> (raw)
In-Reply-To: <20190430144609.19500-1-iker.perez@codethink.co.uk>
On Tue, Apr 30, 2019 at 03:46:07PM +0100, Iker Perez wrote:
> From: Iker Perez del Palomar Sustatxa <iker.perez@codethink.co.uk>
>
> Changes from V2:
> - Correct bad style:
> - Bad assigment, missing spaces before and
> after "=".
> - Divide in two lines longer than 80 characters.
> - Separate dt-bindings and driver-documentation into different
> commits.
>
> Changes from V1:
> - Delete empty lines.
> - Restore replaced tabs by spaces.
>
FWIW, I would expect the change log in the patch(es).
If you want to add a summary like here, its subject should
describe what the patch series does. "Version log" does not
describe the patch series.
> Iker Perez del Palomar Sustatxa (2):
> hwmon: (lm75) Add support for TMP75B
> dt-bindings: hwmon: Add tmp75b to lm75.txt
>
> Documentation/devicetree/bindings/hwmon/lm75.txt | 1 +
> Documentation/hwmon/lm75 | 7 +++++--
> drivers/hwmon/lm75.c | 11 +++++++++++
> 3 files changed, 17 insertions(+), 2 deletions(-)
>
> --
> 2.11.0
prev parent reply other threads:[~2019-04-30 16:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 14:46 [PATCH v3 0/2] Version Log Iker Perez
2019-04-30 14:46 ` [PATCH v3 1/2] hwmon: (lm75) Add support for TMP75B Iker Perez
2019-04-30 16:55 ` Guenter Roeck
2019-04-30 14:46 ` [PATCH v3 2/2] dt-bindings: hwmon: Add tmp75b to lm75.txt Iker Perez
2019-04-30 16:57 ` Guenter Roeck
2019-04-30 16:58 ` Guenter Roeck
2019-04-30 16:56 ` Guenter Roeck [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=20190430165639.GB2699@roeck-us.net \
--to=linux@roeck-us.net \
--cc=iker.perez@codethink.co.uk \
--cc=linux-hwmon@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).