From: James Seo <james@equiv.tech>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: James Seo <james@equiv.tech>, Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
Jonathan Corbet <corbet@lwn.net>,
linux-hwmon@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC 06/11] Documentation/hwmon: Revise patch submission checklist
Date: Fri, 5 May 2023 07:50:40 -0700 [thread overview]
Message-ID: <ZFUXwOlQ73lJDHFr@equiv.tech> (raw)
In-Reply-To: <ZFSHa2ThLorH5fwI@debian.me>
On Fri, May 05, 2023 at 11:34:51AM +0700, Bagas Sanjaya wrote:
> On Thu, May 04, 2023 at 12:57:47AM -0700, James Seo wrote:
>> -* Only the following I2C addresses shall be probed: 0x18-0x1f, 0x28-0x2f,
>> - 0x48-0x4f, 0x58, 0x5c, 0x73 and 0x77. Probing other addresses is strongly
>> - discouraged as it is known to cause trouble with other (non-hwmon) I2C
>> - chips. If your chip lives at an address which can't be probed then the
>> - device will have to be instantiated explicitly (which is always better
>> - anyway.)
>> +* Only the following I2C addresses shall be probed: ``0x18``-``0x1f``,
>> + ``0x28``-``0x2f``, ``0x48``-``0x4f``, ``0x58``, ``0x5c``, ``0x73``,
>> + and ``0x77``. Probing other addresses is strongly discouraged, as it is
>> + known to cause trouble with other (non-``hwmon``) I2C chips. If your chip
>> + lives at an address which can't be probed, then the device will have to be
>> + instantiated explicitly (which is always better anyway).
>
> IMO hwmon here refers to the subsystem (not code identifier name), so
> inlining here isn't needed.
>
>> * Make sure there are no race conditions in the probe function. Specifically,
>> completely initialize your chip and your driver first, then register with
>> - the hwmon subsystem.
>> + the ``hwmon`` subsystem.
>
> Also here.
>
>>
>> -* Use devm_hwmon_device_register_with_info() or, if your driver needs a remove
>> - function, hwmon_device_register_with_info() to register your driver with the
>> - hwmon subsystem. Try using devm_add_action() instead of a remove function if
>> - possible. Do not use any of the deprecated registration functions.
>> +* Use
>> + :ref:`devm_hwmon_device_register_with_info() <devm_hwmon_device_register_with_info>`
>> + or, if your driver needs a remove function,
>> + :ref:`hwmon_device_register_with_info() <hwmon_device_register_with_info>` to
>> + register your driver with the ``hwmon`` subsystem. Try using devm_add_action()
>> + instead of a remove function if possible. Do not use any of the deprecated
>> + registration functions.
>
> And here.
>
>> -* Do not provide support for deprecated sysfs attributes.
>> +* Do not provide support for deprecated ``sysfs`` attributes.
>
> Dunno if sysfs (as subsystem name) also needs to be inlined.
>
> Thanks.
>
> --
> An old man doll... just what I always wanted! - Clara
Good point. I will remove inline references to hwmon and sysfs.
next prev parent reply other threads:[~2023-05-05 14:50 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 7:57 [RFC 00/11] hwmon: Modernize documentation James Seo
2023-05-04 7:57 ` [RFC 01/11] Documentation/hwmon: Move misplaced entry in hwmon docs index James Seo
2023-05-05 4:58 ` Bagas Sanjaya
2023-05-06 13:43 ` Guenter Roeck
2023-05-04 7:57 ` [RFC 02/11] hwmon: (core) Rename last parameter of devm_hwmon_register_with_info() James Seo
2023-05-04 15:29 ` Guenter Roeck
2023-05-05 13:15 ` James Seo
2023-05-05 13:30 ` Guenter Roeck
2023-05-05 14:39 ` James Seo
2023-05-04 7:57 ` [RFC 03/11] hwmon: (core) Revise kerneldoc comments James Seo
2023-07-25 23:51 ` Russell Haley
2023-05-04 7:57 ` [RFC 04/11] Documentation/hwmon: Revise hwmon kernel API reference James Seo
2023-05-05 4:12 ` Bagas Sanjaya
2023-05-05 4:20 ` Bagas Sanjaya
2023-05-05 13:29 ` James Seo
2023-05-06 13:52 ` Guenter Roeck
2023-05-07 14:40 ` James Seo
2023-05-04 7:57 ` [RFC 05/11] Documentation/hwmon: Revise PMBus core documentation James Seo
2023-05-05 4:27 ` Bagas Sanjaya
2023-05-05 4:32 ` Guenter Roeck
2023-05-05 13:35 ` James Seo
2023-05-04 7:57 ` [RFC 06/11] Documentation/hwmon: Revise patch submission checklist James Seo
2023-05-05 4:34 ` Bagas Sanjaya
2023-05-05 14:50 ` James Seo [this message]
2023-05-04 7:57 ` [RFC 07/11] Documentation/hwmon: Revise sysfs interface specification James Seo
2023-05-05 4:51 ` Bagas Sanjaya
2023-05-05 15:01 ` James Seo
2023-05-05 15:10 ` Jonathan Corbet
2023-05-04 7:57 ` [RFC 08/11] Documentation/hwmon: Revise userspace tools documentation James Seo
2023-05-05 5:03 ` Bagas Sanjaya
2023-05-05 15:12 ` James Seo
2023-05-05 21:10 ` Guenter Roeck
2023-05-04 7:57 ` [RFC 09/11] ABI: sysfs-class-hwmon: Revise hwmon ABI documentation James Seo
2023-05-04 7:57 ` [RFC 10/11] hwmon: (core) Add missing beep-related standard attributes James Seo
2023-05-04 7:57 ` [RFC 11/11] ABI: sysfs-class-hwmon: Add missing hwmon " James Seo
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=ZFUXwOlQ73lJDHFr@equiv.tech \
--to=james@equiv.tech \
--cc=bagasdotme@gmail.com \
--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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.