Re: [PATCH] regulator: fix fatal kernel-doc error

[Randy Dunlap]

On 09/17/13 03:32, Mark Brown wrote:
> On Mon, Sep 16, 2013 at 06:08:02PM -0700, Randy Dunlap wrote:
>> From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
>>
>> Fix fatal kernel-doc error in <linux/regulator/driver.h>:
>>
>> Error(include/linux/regulator/driver.h:52): cannot understand prototype: 'struct regulator_linear_range '
> 
> Applied with the first line redone, but this seems like really terrible
> quality of implementation for the kernel-doc stuff - it shouldn't
> explode over something readily copable with like this.  Should we also
> not pick this sort of thing up in -next?

/** means kernel-doc syntax and it was not in proper kernel-doc format,
but maybe it could just be a Warning instead of a fatal Error.

Ideally we should pick it up in -next, of course, but I doubt that anyone
is running kernel-doc on linux-next.  I used to do that, but there are
too many errors/warnings.  I suppose that I could just concentrate on
(fatal) Errors in linux-next and ignore the Warnings.

-- 
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/