public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Chr <chunkeey@web.de>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org,
	Larry Finger <Larry.Finger@lwfinger.net>,
	John W Linville <linville@tuxdriver.com>
Subject: Re: [PATCH] p54: Fix regression due to commit b19fa1f
Date: Thu, 7 Aug 2008 18:34:00 +0200	[thread overview]
Message-ID: <200808071834.00645.mb@bu3sch.de> (raw)
In-Reply-To: <200808071800.58356.chunkeey@web.de>

On Thursday 07 August 2008 18:00:57 Chr wrote:
> On Thursday 07 August 2008 17:27:14 Johannes Berg wrote:
> > On Thu, 2008-08-07 at 17:27 +0200, Chr wrote:
> > > +       u32:24;
> > > +       u32:32;
> > > +       u16:16;
> >
> > That piece looks just wrong though. Bitfields, and in a hw struct?
> well, this is a crude way to silence gcc... without the ":32"
> it complains "warning: declaration does not declare anything".
> 
> Of course we/I can make lot's of u8 paddingZ[X] arrays,
> but we'll run out of Z and X in the long run ;-).


You can use this magic macro:

#define P4D_BYT3S(magic, nr_bytes)	u8 __p4dding##magic[nr_bytes]
#define P4D_BYTES(line, nr_bytes)	P4D_BYT3S(line, nr_bytes)
/* Magic helper macro to pad structures. Ignore those above. It's magic. */
#define PAD_BYTES(nr_bytes)		P4D_BYTES( __LINE__ , (nr_bytes))


struct xyz {
	//foo
	PAD_BYTES(4); /* Pad 4 bytes */
	//bar
};

-- 
Greetings Michael.

  reply	other threads:[~2008-08-07 16:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-07 13:21 [PATCH] p54: Fix regression due to commit b19fa1f Larry Finger
2008-08-07 13:27 ` Johannes Berg
2008-08-07 15:20   ` Larry Finger
2008-08-07 15:27   ` Chr
2008-08-07 15:26     ` Johannes Berg
2008-08-07 15:27     ` Johannes Berg
2008-08-07 16:00       ` Chr
2008-08-07 16:34         ` Michael Buesch [this message]
2008-08-07 15:59     ` Larry Finger
2008-08-07 23:18       ` Chr
  -- strict thread matches above, loose matches on Subject: below --
2008-08-04 21:14 Larry Finger
2008-08-06 22:57 ` Chr
2008-08-07  3:33   ` Larry Finger
2008-08-07  7:33     ` Chr
2008-08-07  6:35   ` Johannes Berg

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=200808071834.00645.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=Larry.Finger@lwfinger.net \
    --cc=chunkeey@web.de \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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