[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALAqxLXerF=g3=axbe8xsbmQg-5SxU0w06cqup0oaq4Dr6bBig@mail.gmail.com>
Date: Wed, 9 Dec 2015 13:42:16 -0800
From: John Stultz <john.stultz@...aro.org>
To: Sascha Hauer <s.hauer@...gutronix.de>
Cc: Arnd Bergmann <arnd@...db.de>, lkml <linux-kernel@...r.kernel.org>,
Rob Herring <robh+dt@...nel.org>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
Vinay Simha BN <simhavcs@...il.com>,
Bjorn Andersson <bjorn.andersson@...ymobile.com>,
Haojian Zhuang <haojian.zhuang@...aro.org>,
devicetree@...r.kernel.org,
Android Kernel Team <kernel-team@...roid.com>
Subject: Re: [RFC][PATCH] misc: Introduce reboot_reason driver
On Wed, Dec 9, 2015 at 12:50 AM, Sascha Hauer <s.hauer@...gutronix.de> wrote:
> On Tue, Dec 08, 2015 at 04:13:35PM -0800, John Stultz wrote:
>>
>> Is there a better way? Are enums for array indexes out of fashion?
>
> They are not, but you have declared a variable (reason_types) which you
> don't use. You probably meant to create a enum named reason_types, like
> this:
>
> enum reason_types {
> NONE,
> BOOTLOADER,
> RECOVERY,
> OEM,
> MAX_REASONS
> };
So I had tried using a enum name as well, close to what you suggest
here, and still got the "warning: useless storage class specifier in
empty declaration" build warning.
Though trying again, it seems the problem was I was declaring it as
"static enum ...". Removing the static allows it to build w/o warnings
as a unnamed enum structure. Why, I don't know. :P
Thanks for the pointer!
-john
--
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