From: Ivor Wanders <ivor@iwanders.net>
To: rdunlap@infradead.org
Cc: corbet@lwn.net, ivor@iwanders.net, jdelvare@suse.com,
linux-doc@vger.kernel.org, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org, linux@roeck-us.net,
luzmaximilian@gmail.com
Subject: Re: [PATCH v2] hwmon: clarify intent of fan min/max
Date: Thu, 21 Dec 2023 18:46:46 -0500 [thread overview]
Message-ID: <20231221234646.15776-1-ivor@iwanders.net> (raw)
In-Reply-To: <6ec27515-d2c1-48f1-8935-55f0ae48e72b@infradead.org>
> (other than telling us what changed from v1 to v2)
Appreciate the feedback! I'm new to this, so basically it means always
use --cover-letter, I also noticed that I should have probably added some
'to' entries, the command suggested by lore moved the original 'to' fields
to 'cc'. I'll be more diligent with the changelog in future contributions.
Change was incorporating the feedback from [1], changing the comma into a
period for all three changed sysfs entries.
~Ivor
[1]: https://lore.kernel.org/linux-hwmon/40285311-8adc-4ca9-86ce-27c8b723a102@infradead.org/
next prev parent reply other threads:[~2023-12-21 23:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 22:51 [PATCH 0/1] clarify intent of fan min and max attributes Ivor Wanders
2023-12-21 22:51 ` [PATCH 1/1] hwmon: clarify intent of fan min/max Ivor Wanders
2023-12-21 23:19 ` Randy Dunlap
2023-12-21 23:31 ` [PATCH v2] " Ivor Wanders
2023-12-21 23:38 ` Randy Dunlap
2023-12-21 23:46 ` Ivor Wanders [this message]
2023-12-22 16:14 ` Guenter Roeck
2023-12-22 23:20 ` Ivor Wanders
2023-12-22 16:12 ` [PATCH 0/1] clarify intent of fan min and max attributes Guenter Roeck
2023-12-22 23:17 ` Ivor Wanders
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=20231221234646.15776-1-ivor@iwanders.net \
--to=ivor@iwanders.net \
--cc=corbet@lwn.net \
--cc=jdelvare@suse.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=luzmaximilian@gmail.com \
--cc=rdunlap@infradead.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