From: Jean Delvare <khali@linux-fr.org>
To: "Mark M. Hoffman" <mhoffman@lightlink.com>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>,
lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] [RFC][PATCH] hwmon:fix sparse warnings + error handling
Date: Mon, 21 Aug 2006 11:11:27 +0200 [thread overview]
Message-ID: <20060821111127.fe93bc0a.khali@linux-fr.org> (raw)
In-Reply-To: <20060821023017.GA30017@jupiter.solarsys.private>
Mark, Michal,
> Thanks for doing this... but Andrew please don't apply it. The sensors project
> people are working on these even now, and we already have a patch for the
> w83627hf driver...
>
> http://lists.lm-sensors.org/pipermail/lm-sensors/2006-August/017204.html
>
> Jean Delvare (hwmon maintainer) should be sending these up the chain soon.
>
> Michal: if you're interested in fixing any of the rest of them, please take
> a look at the patch above to see the mechanism we intend to use. It actually
> makes the drivers *smaller* than they were.
The size change really depends on the driver. For older drivers with
individual file registration (sometimes hidden behind macros) the
driver size will indeed shrink, but for newer drivers with loop-based
file registration, this would be a slight increase in size. Not that it
really matters anyway, what matters is that we handle errors and file
deletion properly from now on.
Michal, if you go on working on this (and this is welcome), please
follow what Mark did, as this is what we agreed was the best approach.
Here is a quick status summary for drivers/hwmon:
Done by Mark M. Hoffman:
o asb100
o lm75
o lm78
o smsc47b397
o w83627hf
Done by Jim Cromie:
o pc87360
Will be done by David Hubbard:
o w83627ehf
Will be done by me:
o f71805f
o it87
o lm63
o lm83
o lm90
This leaves the following list:
o abituguru
o adm1021
o adm1025
o adm1026
o adm1031
o adm9240
o atxp1
o ds1621
o fscher
o fscpos
o gl518sm
o gl520sm
o lm77
o lm80
o lm85
o lm87
o lm92
o max1619
o sis5595
o smsc47m1
o smsc47m192
o via686a
o vt8231
o w83781d
o w83791d
o w83792d
o w83l785ts
Almost 1000 warnings for drivers/hwmon alone... OTOH I wonder how
device_create_file and friends qualified for __must_check given that
nothing wrong can happen if they fail, from the kernel's point of view.
The files are not created and that's about it.
If you are going to fix some of the drivers listed above, please
advertise on the lm-sensors list so that your work is not duplicated.
As a side note, I have patches ready for everything under drivers/i2c
already, I sent them on the i2c list last week and will push them soon
now.
Thanks,
--
Jean Delvare
next prev parent reply other threads:[~2006-08-21 9:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-20 20:44 [RFC][PATCH] hwmon:fix sparse warnings + error handling Michal Piotrowski
2006-08-20 21:49 ` [lm-sensors] " jim.cromie
2006-08-20 22:12 ` Michal Piotrowski
2006-08-20 22:28 ` Alan Cox
2006-08-21 2:30 ` [lm-sensors] " Mark M. Hoffman
2006-08-21 9:11 ` Jean Delvare [this message]
2006-08-21 16:46 ` Grant Coady
2006-08-21 8:04 ` Jean Delvare
2006-08-22 0:43 ` Dmitry Torokhov
2006-08-22 11:34 ` Mark M. Hoffman
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=20060821111127.fe93bc0a.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=mhoffman@lightlink.com \
--cc=michal.k.k.piotrowski@gmail.com \
/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