From: Krzysztof Kozlowski <krzk@kernel.org>
To: Andrei Lalaev <andrey.lalaev@gmail.com>
Cc: jdelvare@suse.com, linux@roeck-us.net, conor+dt@kernel.org,
krzk+dt@kernel.org, robh@kernel.org, linux-hwmon@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] hwmon: add driver for HTU31
Date: Mon, 27 Jan 2025 13:16:22 +0100 [thread overview]
Message-ID: <4bcc6282-4ebc-48a1-8644-ef2c322e0441@kernel.org> (raw)
In-Reply-To: <9c2bcef2-4e8c-4856-9a49-1f02110284a5@gmail.com>
On 24/01/2025 15:56, Andrei Lalaev wrote:
> On 24.01.2025 09:31, Krzysztof Kozlowski wrote:
>> On Thu, Jan 23, 2025 at 09:25:06PM +0100, Andrei Lalaev wrote:
>>> ibmpowernv
>>> diff --git a/drivers/hwmon/Kconfig b/drivers/hwmon/Kconfig
>>> index 4cbaba15d86e..e123e06ba352 100644
>>> --- a/drivers/hwmon/Kconfig
>>> +++ b/drivers/hwmon/Kconfig
>>> @@ -789,6 +789,17 @@ config SENSORS_HS3001
>>> This driver can also be built as a module. If so, the module
>>> will be called hs3001.
>>>
>>
>> Looks like you add here stray spaces.
>>
>
> Could you please explain what you mean? I see only 1 tab and 2 spaces right after it,
> but they were here even before my patch.
Diff in mutt looked like having stray spaces added in this hunk. Exactly
that line I commented under, not in some other place. There was no tab
and 2 spaces.
If you double checked and are sure there is no stray space, then fine.
Could be just mutt....
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-01-27 12:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 20:25 [PATCH 0/2] Add driver for HTU31 Andrei Lalaev
2025-01-23 20:25 ` [PATCH 1/2] hwmon: add " Andrei Lalaev
2025-01-24 8:31 ` Krzysztof Kozlowski
2025-01-24 14:56 ` Andrei Lalaev
2025-01-27 12:16 ` Krzysztof Kozlowski [this message]
2025-01-24 12:14 ` Christophe JAILLET
2025-01-23 20:25 ` [PATCH 2/2] dt-bindings: hwmon: Add description for sensor HTU31 Andrei Lalaev
2025-01-24 8:26 ` Krzysztof Kozlowski
-- strict thread matches above, loose matches on Subject: below --
2025-01-26 14:40 [PATCH v2 0/2] Add driver for HTU31 Andrei Lalaev
2025-01-26 14:40 ` [PATCH 1/2] hwmon: add " Andrei Lalaev
2025-01-26 14:59 ` Guenter Roeck
2025-01-26 19:16 ` Andrei Lalaev
2025-01-26 19:36 ` Guenter Roeck
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=4bcc6282-4ebc-48a1-8644-ef2c322e0441@kernel.org \
--to=krzk@kernel.org \
--cc=andrey.lalaev@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=krzk+dt@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh@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