[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0705020344480.6259@localhost.localdomain>
Date: Wed, 2 May 2007 03:47:26 -0400 (EDT)
From: "Robert P. J. Day" <rpjday@...dspring.com>
To: David Rientjes <rientjes@...gle.com>
cc: Alexey Dobriyan <adobriyan@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org
Subject: Re: [patch 01/10] compiler: define __attribute_unused__
On Wed, 2 May 2007, David Rientjes wrote:
> On Wed, 2 May 2007, Robert P. J. Day wrote:
>
> > not only that, but there are numerous files that *already* use
> > "__unused":
> >
> > $ grep -rw __unused *
> > ... snip lots of output here ...
> >
> > as well as a few files that can now have their definition of that
> > removed:
> >
> > $ grep -r "define __unused" *
> > drivers/net/defxx.c:#define __unused __attribute__ ((unused))
> > drivers/net/declance.c:#define __unused __attribute__ ((unused))
> > drivers/misc/thinkpad_acpi.c:#define __unused __attribute__ ((unused))
> >
> > i think "__unused" is the clear choice here.
> >
>
> No, it's not the clear choice. This would apply to both functions
> and variables so the suppress a compiler warning for a variable
> whose use depends on preprocessor macros, I would have to use
> __unused even though it may be used.
>
> Hence, I recommend __maybe_unused.
sorry, i worded that badly. i suggested that "__unused" was the clear
choice only because it already had significant historical precedent
and people on this list are notorious for not liking major, disruptive
changes.
if no one objects to changing the existing occurrences, then no
problem.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
-
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