[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080326100336.GE22584@shadowen.org>
Date: Wed, 26 Mar 2008 10:03:36 +0000
From: Andy Whitcroft <apw@...dowen.org>
To: Dean Nelson <dcn@....com>
Cc: rdunlap@...otime.net, jschopp@...tin.ibm.com, jes@....com,
linux-kernel@...r.kernel.org, tony.luck@...el.com,
linux-ia64@...r.kernel.org
Subject: Re: [Patch 5/5] run drivers/misc/xp through scripts/checkpatch.pl
On Tue, Mar 25, 2008 at 03:05:17PM -0500, Dean Nelson wrote:
> On Tue, Mar 25, 2008 at 02:25:29PM -0500, dcn@....com wrote:
> >
> > Addressed issues raised by scripts/checkpatch.pl. Removed unnecessary curly
> > braces. Eliminated uses of volatiles and use of kernel_thread() and
> > daemonize().
> >
> > Signed-off-by: Dean Nelson <dcn@....com>
> >
>
> Forgot to mention that scripts/checkpatch.pl gave 15 false positives of
> the following type against drivers/misc/xp/xp_main.c.
>
> > WARNING: EXPORT_SYMBOL(foo); should immediately follow its function/variable
> > #48: FILE: misc/xp/xp_main.c:48:
> > +EXPORT_SYMBOL_GPL(xp_remote_memcpy);
>
> The fact is that the EXPORT_SYMBOL(xp_remote_memcpy) does immediately follow
> the function/variable as follows.
>
> enum xp_retval (*xp_remote_memcpy) (void *dst, const void *src, size_t len);
> EXPORT_SYMBOL_GPL(xp_remote_memcpy);
Gah, who ever came up with that syntax. Yep, thats a falsie. Should be
fixed in the latest version:
http://www.kernel.org/pub/linux/kernel/people/apw/checkpatch/checkpatch.pl-next
Thanks for the report.
-apw
--
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