From: Marcel Holtmann <marcel@holtmann.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Daryl Van Vorst <daryl@wideray.com>,
"'BlueZ Mailing List'" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Alignment issue
Date: Sun, 23 Jan 2005 16:22:35 +0100 [thread overview]
Message-ID: <1106493755.9269.17.camel@pegasus> (raw)
In-Reply-To: <1106493068.6480.12.camel@localhost.localdomain>
Hi David,
> > patch is now in the CVS and everything seems fine again. Btw what is the
> > difference between typeof and __typeof__. The latter one is used by the
> > previous macro and you used the other?
>
> There's no difference. It's just like 'inline' and '__inline__'.
and what is the prefered one? I would use __typeof__, because the
previous version did so. However I am not a compiler expert.
> > Fine with me, but then I simply replace it with bt_{get|put}unaligned
> > and remove the complete stuff. There is no external user
> > sdp_interal.h.
All done by now :)
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-01-23 15:22 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 18:38 [Bluez-devel] Alignment issue Daryl Van Vorst
2004-08-10 23:12 ` Marcel Holtmann
2004-08-11 9:20 ` Stephen Crane
2004-08-11 11:08 ` David Woodhouse
2004-08-11 19:33 ` Marcel Holtmann
2004-08-11 7:13 ` Marcel Holtmann
2004-08-11 16:44 ` Daryl Van Vorst
2004-08-11 19:31 ` Marcel Holtmann
2004-08-12 8:34 ` David Woodhouse
2004-08-12 9:27 ` Marcel Holtmann
2004-08-12 10:01 ` David Woodhouse
2004-08-12 10:22 ` Marcel Holtmann
2004-08-12 10:35 ` David Woodhouse
2004-08-12 11:00 ` Marcel Holtmann
2004-08-12 11:33 ` David Woodhouse
2004-08-12 11:49 ` Marcel Holtmann
2004-08-12 12:02 ` David Woodhouse
2004-08-12 12:29 ` Marcel Holtmann
2004-08-12 13:36 ` Marcel Holtmann
2004-08-13 8:07 ` David Woodhouse
2004-08-13 9:05 ` Marcel Holtmann
2004-08-13 9:14 ` David Woodhouse
2004-08-13 11:52 ` David Woodhouse
2004-08-13 12:40 ` Marcel Holtmann
2004-08-12 12:53 ` David Woodhouse
2004-08-13 9:58 ` Marcel Holtmann
2004-08-13 10:56 ` David Woodhouse
2004-08-12 10:10 ` Stephen Crane
2004-08-12 10:25 ` Marcel Holtmann
2005-01-20 14:30 ` David Woodhouse
2005-01-20 14:45 ` Marcel Holtmann
2005-01-20 14:59 ` David Woodhouse
2005-01-20 18:14 ` Marcel Holtmann
2005-01-21 8:26 ` David Woodhouse
2005-01-23 8:12 ` Marcel Holtmann
2005-01-23 11:39 ` Marcel Holtmann
2005-01-23 12:29 ` David Woodhouse
2005-01-23 14:40 ` Marcel Holtmann
2005-01-23 15:11 ` David Woodhouse
2005-01-23 15:22 ` Marcel Holtmann [this message]
2005-01-23 23:16 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2004-08-16 9:48 john smith
2004-08-16 10:15 ` Marcel Holtmann
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=1106493755.9269.17.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=daryl@wideray.com \
--cc=dwmw2@infradead.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