From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Marcus Folkesson <marcus.folkesson@gmail.com>
Cc: Kent Gustavsson <kent@minoris.se>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/9] Improve MCP3911 driver
Date: Wed, 17 Aug 2022 09:12:32 +0300 [thread overview]
Message-ID: <35973b74-f8f2-f953-f937-365acb67db43@linaro.org> (raw)
In-Reply-To: <YvuwTVlgTeDvCTi+@gmail.com>
On 16/08/2022 17:57, Marcus Folkesson wrote:
> On Tue, Aug 16, 2022 at 01:22:31PM +0300, Krzysztof Kozlowski wrote:
>> On 15/08/2022 09:16, Marcus Folkesson wrote:
>>> v5:
>>> - Drop remove function
>>> - Split tx&rx transfers in mcp3911_trigger_handler()
>>> - Moved Kconfig changes to right patch
>>>
>>> v6:
>>> - Go for devm_clk_get_enabled()
>>> - Cosmetic cleanups
>>> - Clarify the description of microchip,data-ready-hiz
>>>
>>
>> Please include the diffstat (format-patch does it for you, but if you
>> prefer to use other tools - it's your job).
>
> I'm sorry, I do not get you.
> The diffstat is included in the patches, should it be included here as
> well?
Yes, in the cover letter, so when someone partially interested (e.g. me)
opens the cover letter, it's easy to notice what files are affected.
Again, this is exactly what Git is doing, so you have to on purpose use
less-standard process to achieve cover letter without diffstat.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-08-17 6:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 6:16 [PATCH v6 0/9] Improve MCP3911 driver Marcus Folkesson
2022-08-15 6:16 ` [PATCH v6 1/9] iio: adc: mcp3911: make use of the sign bit Marcus Folkesson
2022-08-15 6:16 ` [PATCH v6 2/9] iio: adc: mcp3911: correct "microchip,device-addr" property Marcus Folkesson
2022-08-15 6:16 ` [PATCH v6 3/9] iio: adc: mcp3911: use correct formula for AD conversion Marcus Folkesson
2022-08-15 6:16 ` [PATCH v6 4/9] iio: adc: mcp3911: use resource-managed version of iio_device_register Marcus Folkesson
2022-08-20 12:41 ` Jonathan Cameron
2022-09-12 11:02 ` Marcus Folkesson
2022-09-19 15:36 ` Jonathan Cameron
2022-09-21 20:13 ` Jonathan Cameron
2022-08-15 6:16 ` [PATCH v6 5/9] iio: adc: mcp3911: add support for buffers Marcus Folkesson
2022-08-15 6:16 ` [PATCH v6 6/9] iio: adc: mcp3911: add support for interrupts Marcus Folkesson
2022-08-15 6:16 ` [PATCH v6 7/9] dt-bindings: iio: adc: mcp3911: add microchip,data-ready-hiz entry Marcus Folkesson
2022-08-15 6:16 ` [PATCH v6 8/9] iio: adc: mcp3911: add support for oversampling ratio Marcus Folkesson
2022-08-15 6:16 ` [PATCH v6 9/9] iio: adc: mcp3911: add support to set PGA Marcus Folkesson
2022-08-16 10:22 ` [PATCH v6 0/9] Improve MCP3911 driver Krzysztof Kozlowski
2022-08-16 14:57 ` Marcus Folkesson
2022-08-17 6:12 ` Krzysztof Kozlowski [this message]
2022-08-17 16:08 ` Marcus Folkesson
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=35973b74-f8f2-f953-f937-365acb67db43@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=kent@minoris.se \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcus.folkesson@gmail.com \
--cc=robh+dt@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).