From: Guenter Roeck Date: Sat, 31 Jul 2010 01:13:39 +0000 Subject: Re: [lm-sensors] [PATCH V3 2/5] Package Level Thermal Control and Message-Id: <20100731011339.GB28386@ericsson.com> List-Id: References: <1280448826-12004-1-git-send-email-fenghua.yu@intel.com> <1280448826-12004-3-git-send-email-fenghua.yu@intel.com> <4C537514.9090109@zytor.com> In-Reply-To: <4C537514.9090109@zytor.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: "H. Peter Anvin" Cc: Fenghua Yu , Ingo Molnar , Thomas Gleixner , Len Brown , Chen Gong , Jean Delvare , Huaxu Wan , linux-kernel , lm-sensors On Fri, Jul 30, 2010 at 08:57:56PM -0400, H. Peter Anvin wrote: > On 07/29/2010 05:13 PM, Fenghua Yu wrote: > > + > > +enum { SHOW_TEMP, SHOW_TJMAX, SHOW_TTARGET, SHOW_LABEL, SHOW_NAME } SHOW; > > + > > This conflicts with an equally poorly named global variable in > drivers/hwmon/via-cputemp.c, and the conflict is causing a build failure. > > I think both these drivers have the same bug: a missing "typedef" before > the enum keyword, as present in coretemp.c. Of course, one can question > if it should be given a typename at all since in none of these drivers Especially since it isn't really a type name, but a global variable named SHOW. Type name (also called tag) would be enum SHOW { ... }; . Guenter > they are actually referenced by type, and instead the enumeration is > just used as a source of constants, which can perfectly well be handled > with an unnamed enum: > > enum { SHOW_TEMP, SHOW_TJMAX, SHOW_TTARGET, SHOW_LABEL, SHOW_NAME }; > > -hpa _______________________________________________ lm-sensors mailing list lm-sensors@lm-sensors.org http://lists.lm-sensors.org/mailman/listinfo/lm-sensors