[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8bd0f97a1001191352n4968bebep2342912c571595fa@mail.gmail.com>
Date: Tue, 19 Jan 2010 16:52:21 -0500
From: Mike Frysinger <vapier.adi@...il.com>
To: Joe Perches <joe@...ches.com>
Cc: Wim Van Sebroeck <wim@...ana.be>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Andrew Morton <akpm@...ux-foundation.org>,
Florian Fainelli <florian@...nwrt.org>,
Russell King <rmk+kernel@....linux.org.uk>,
Mark Brown <broonie@...nsource.wolfsonmicro.com>,
LKML <linux-kernel@...r.kernel.org>, linuxppc-dev@...abs.org,
uclinux-dist-devel@...ckfin.uclinux.org, linux-omap@...r.kernel.org
Subject: Re: [RFC] [PATCH] watchdog_info separation and constify
On Tue, Jan 19, 2010 at 16:42, Joe Perches wrote:
> On Tue, 2010-01-19 at 22:17 +0100, Wim Van Sebroeck wrote:
>> -static struct watchdog_info at32_wdt_info = {
>> +static const struct watchdog_info at32_wdt_info = {
>
> It'd be good to use a consistent structure name:
>
> static const struct watchdog_info ident = {
> etc...
> }
i'd agree (obviously i'm partial to the "xxx_wdt_info" form), but i'd
worry about this after the watchdog implementations are finally
unified ... might be less code needing standardization at that point
-mike
--
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