From: Joe Perches <joe@perches•com>
To: Guenter Roeck <linux@roeck-us•net>, Jean Delvare <jdelvare@suse•com>
Cc: linux-hwmon@vger•kernel.org, linux-kernel@vger•kernel.org,
linuxppc-dev@lists•ozlabs.org,
linux-arm-kernel@lists•infradead.org,
patches@opensource•cirrus.com
Subject: Re: [PATCH script] hwmon: Use octal not symbolic permissions
Date: Tue, 27 Mar 2018 04:48:05 -0700 [thread overview]
Message-ID: <1522151285.12357.78.camel@perches.com> (raw)
In-Reply-To: <5ec8703b-2979-7a1d-fbc3-bd528d7a5e29@roeck-us.net>
On Tue, 2018-03-27 at 03:28 -0700, Guenter Roeck wrote:
> On 03/27/2018 12:35 AM, Joe Perches wrote:
> > On Mon, 2018-03-26 at 23:33 -0700, Guenter Roeck wrote:
> > > Since the hwmon subsystem has been labeled as both "obsolete" and "obscure",
> >
> > fyi: It's marked Maintained in MAINTAINERS
> >
>
> I did not say that it was not maintained, and I am aware of the information
> in the MAINTAINERS file, thanks.
As am I.
I do agree that hwmon is obscure. Almost everything about
anything is obscure to those that don't fully understand it.
I am unaware though of any use of "obsolete" in drivers/hwmon/
or in Documentation/ about hwmon or the wiki/
In what sense do you mean hwmon is obsolete?
And the cocci script?
Anything later than:
https://systeme.lip6.fr/pipermail/cocci/2016-December/003887.html
https://github.com/groeck/coccinelle-patches/tree/master/hwmon
?
btw: I think the perl scripts I posted for DEV_ATTR_<RW|RO|WO>
transforms are simpler and less prone to tool versioning
issues.
https://lkml.org/lkml/2017/12/22/844
It'd be fairly simple to add SENSOR_ support.
next prev parent reply other threads:[~2018-03-27 11:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 20:28 [PATCH script] hwmon: Use octal not symbolic permissions Joe Perches
2018-03-27 6:33 ` Guenter Roeck
2018-03-27 6:52 ` Joe Perches
2018-03-27 7:35 ` Joe Perches
2018-03-27 10:28 ` Guenter Roeck
2018-03-27 11:48 ` Joe Perches [this message]
2018-03-27 15:44 ` Guenter Roeck
2018-03-27 16:52 ` Joe Perches
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=1522151285.12357.78.camel@perches.com \
--to=joe@perches$(echo .)com \
--cc=jdelvare@suse$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-hwmon@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux@roeck-us$(echo .)net \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=patches@opensource$(echo .)cirrus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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