From: Dave Jones <davej@redhat.com>
To: Jan Blunck <jblunck@suse.de>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] Eliminate __attribute__ ((packed)) warnings for gcc-4.1
Date: Tue, 3 Jan 2006 21:25:30 -0500 [thread overview]
Message-ID: <20060104022530.GA29784@redhat.com> (raw)
In-Reply-To: <20060103113045.GB24131@hasse.suse.de>
On Tue, Jan 03, 2006 at 12:30:45PM +0100, Jan Blunck wrote:
> typedef struct T30_s {
> /* session parameters */
> - __u8 resolution __attribute__ ((packed));
> - __u8 rate __attribute__ ((packed));
> - __u8 width __attribute__ ((packed));
> - __u8 length __attribute__ ((packed));
> - __u8 compression __attribute__ ((packed));
> - __u8 ecm __attribute__ ((packed));
> - __u8 binary __attribute__ ((packed));
> - __u8 scantime __attribute__ ((packed));
> - __u8 id[FAXIDLEN] __attribute__ ((packed));
> + __u8 resolution;
> + __u8 rate ;
> + __u8 width ;
> + __u8 length ;
> + __u8 compression ;
> + __u8 ecm ;
> + __u8 binary ;
> + __u8 scantime ;
> + __u8 id[FAXIDLEN] ;
What's with the funky placement of ; ?
The rest of the struct looks sensible.
>
> /* various cruft */
> - u32 dataA[6] __attribute((packed));
> - u16 dataB[5] __attribute((packed));
> - u32 dataC[14] __attribute((packed));
> -};
> + u32 dataA[6];
> + u16 dataB[5];
> + u32 dataC[14];
> +} __attribute((packed));
You could fix the horked indentation at the same time.
(This crops up in a few places in this diff)
Dave
next prev parent reply other threads:[~2006-01-04 2:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-03 11:30 [PATCH 1/3] Eliminate __attribute__ ((packed)) warnings for gcc-4.1 Jan Blunck
2006-01-04 2:25 ` Dave Jones [this message]
2006-01-04 9:15 ` Jan Engelhardt
2006-01-04 10:55 ` Jan Blunck
2006-01-04 10:56 ` Eliminate __attribute__ ((packed)) warnings for gcc-4.1 (whitespace-beautified version) Jan Blunck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060104022530.GA29784@redhat.com \
--to=davej@redhat.com \
--cc=akpm@osdl.org \
--cc=jblunck@suse.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox