[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111006190752.GA28455@ericsson.com>
Date: Thu, 6 Oct 2011 12:07:52 -0700
From: Guenter Roeck <guenter.roeck@...csson.com>
To: Greg KH <greg@...ah.com>
CC: Himanshu Chauhan <hschauhan@...ltrace.org>,
"lm-sensors@...sensors.org" <lm-sensors@...sensors.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"kernelnewbies@...nelnewbies.org" <kernelnewbies@...nelnewbies.org>
Subject: Re: [lm-sensors] [PATCH] hwmon class driver registration with a
device number
On Thu, Oct 06, 2011 at 02:25:00PM -0400, Greg KH wrote:
> On Thu, Oct 06, 2011 at 09:40:11AM +0530, Himanshu Chauhan wrote:
> > Hi Greg,
> >
> > >
> > > How do you later remove a device created with this new interface? As it
> > > is, I think the existing calls will fail, right?
> > >
> > If I have not missed out anything from hwmon_device_unregister(), it shouldn't
> > fail. Why did you point that out?
>
> If you create a device with a call to device_create() with a dev_t set,
> it is usually cleaned up with a call to device_destroy(), but you are
> right, a simple call to device_unregister() will still work properly.
>
> So nevermind, sorry for the noise.
>
Not entirely noise. Since the new registration call is not exported in the patch,
any code using it won't be compilable as module, which in turn means
that hwmon_device_unregister() was never called.
So while we know that it _should_ work, we also know that it was not tested.
> What you do need to determine is if this is a device node you really
> want to be creating in this manner, as it is a new user/kernel API,
> right?
>
And why, and what for.
Guenter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists