From: Jean Delvare <khali@linux-fr.org>
To: Hans de Goede <j.w.r.degoede@hhs.nl>
Cc: Jeff Garzik <jeff@garzik.org>, Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] hwmon/abituguru: handle sysfs errors
Date: Sat, 2 Dec 2006 12:36:18 +0100 [thread overview]
Message-ID: <20061202123618.67047029.khali@linux-fr.org> (raw)
In-Reply-To: <452B6569.7050404@hhs.nl>
Hans,
On Tue, 10 Oct 2006 11:18:33 +0200, Hans de Goede wrote:
> Jean Delvare wrote:
> > The patch isn't wrong per se, but it could be made more simple, and is
> > incomplete in comparison to what was done for all other hardware
> > monitoring drivers:
> >
> > * We want to create all the files before registering with the hwmon
> > class, this closes a race condition.
> > * We want to delete all the device files at regular cleanup time (after
> > unregistering with the hwmon class).
> > * It's OK to call device_remove_file() on a non-existent file, so the
> > error path can be simplified.
> >
> > I'd like the abituguru driver to behave the same as all other hardware
> > monitoring drivers to lower the maintenance effort. Can either you
> > or Jeff work up a compliant patch?
>
> I understand Jeff any chance you can do a new revision of
> your patch? Otherwise I'll take care of it as time permits.
I'm still waiting for this patch. It'd be nice to have the abituguru
driver fixed in 2.6.20.
Thanks,
--
Jean Delvare
prev parent reply other threads:[~2006-12-02 11:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 6:53 [PATCH] hwmon/abituguru: handle sysfs errors Jeff Garzik
2006-10-10 7:27 ` Hans de Goede
2006-10-10 9:08 ` Jean Delvare
2006-10-10 9:18 ` Hans de Goede
2006-10-10 9:34 ` Jean Delvare
2006-10-12 4:31 ` Dmitry Torokhov
2006-10-12 15:42 ` Jean Delvare
2006-10-16 3:56 ` Dmitry Torokhov
2006-12-02 11:36 ` Jean Delvare [this message]
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=20061202123618.67047029.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=akpm@osdl.org \
--cc=j.w.r.degoede@hhs.nl \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.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 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.