[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D948624.3040605@suse.cz>
Date: Thu, 31 Mar 2011 15:48:20 +0200
From: Jiri Slaby <jslaby@...e.cz>
To: Arnd Bergmann <arnd@...db.de>
CC: Arend van Spriel <arend@...adcom.com>,
linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
rmk+kernel@....linux.org.uk, devel@...uxdriverproject.org,
gregkh@...e.de, linux-wireless@...r.kernel.org,
Jiri Slaby <jirislaby@...il.com>
Subject: Re: [PATCH 1/1] drivers: brcmaxi: provide amba axi functionality
in separate module
On 03/30/2011 02:53 PM, Arnd Bergmann wrote:
> On Tuesday 29 March 2011, Jiri Slaby wrote:
>> On 03/29/2011 11:40 AM, Arend van Spriel wrote:
>>> --- /dev/null
>>> +++ b/drivers/brcmaxi/axi.c
>>> @@ -0,0 +1,786 @@
>> ...
>>> +/* resetctrl */
>>> +#define AIRC_RESET 1
>>> +
>>> +/* definition for specifying padding fields */
>>> +#define _PADLINE(line) pad ## line
>>> +#define _XSTR(line) _PADLINE(line)
>>> +#define PAD _XSTR(__LINE__)
>>> +
>>> +/*
>>> + * struct aidmp - device management plugin "wrapper" registers.
>>> + */
>>> +struct aidmp {
>>
>> This looks like it should be __packed__.
>
> Why that? Adding the packed attribute would enforce byte access but
> not change the layout of the structure, so I think that would make
> it worse not better.
How it can? Packed only tells the compiler to have one byte alignment
steps. And it should not matter here as all the members are 32-bit long.
The structure seems to be something which maps to device registers. So
for documentation purposes it should be packed. And to avoid later
mistakes when the u32 are broken down to u8s and u16s.
regards,
--
js
suse labs
--
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