[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130215.152025.1605170079652952030.davem@davemloft.net>
Date: Fri, 15 Feb 2013 15:20:25 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: joe@...ches.com
Cc: mugunthanvnm@...com, netdev@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-omap@...r.kernel.org
Subject: Re: [PATCH v2 1/1] drivers: net: davinci_cpdma: acknowledge
interrupt properly
From: Joe Perches <joe@...ches.com>
Date: Fri, 15 Feb 2013 12:18:59 -0800
> On Fri, 2013-02-15 at 15:05 -0500, David Miller wrote:
>> From: Mugunthan V N <mugunthanvnm@...com>
>> Date: Thu, 14 Feb 2013 23:56:46 +0530
>>
>> > +enum {
>> > + CPDMA_EOI_RX_THRESH = 0,
>> > + CPDMA_EOI_RX,
>> > + CPDMA_EOI_TX,
>> > + CPDMA_EOI_MISC,
>> > +};
>>
>> Do not use enumerations for hardware register values, which must be
>> exact, otherwise you are potentially going to succumb to the vagaries
>> of C language enumeration value assignment.
>
> Vagaries?
>
> In what way is c enumeration (6.7.2.2) vague?
> char vs int? Isn't smaller mostly better?
>
> Concern about possible future reordering given an
> insertion or deletion might be the only consideration
> I could imagine.
Right. That's why you should use explicit CPP defines for
register offsets and values.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists