[PATCH 1/3] drivers: misc: add omap_hwspinlock driver
ohad at wizery.com
Tue Oct 19 16:18:57 EDT 2010
On Tue, Oct 19, 2010 at 5:46 PM, Greg KH <greg at kroah.com> wrote:
> On Mon, Oct 18, 2010 at 09:44:33AM +0200, Ohad Ben-Cohen wrote:
>> +#else /* !CONFIG_OMAP_HWSPINLOCK */
>> +static inline struct omap_hwspinlock *omap_hwspinlock_request(void)
>> + return ERR_PTR(-ENOSYS);
> One note, do you really want to fail if this option isn't built into the
> kernel, yet you have a driver that is asking for it? Shouldn't you
> instead just silently succeed, and let the code path get compiled away?
> We did that for debugfs, after learning the pain that procfs had with
> its api for "is not built". Doing it the way you are requires the user
> to always test for -ENOSYS, when in reality, if that is returned,
> there's nothing the driver can do about it, so it should just not worry
> about it.
> Just something to think about.
Completely agree; if hwspinlock support is not needed, we better let
its users run uninterruptedly. I'll change it.
> greg k-h
More information about the linux-arm-kernel