From: Johan Hedberg <johan.hedberg@gmail.com>
To: Anderson Lizardo <anderson.lizardo@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] Fix strict-aliasing rules handling for hciemu and IP ports
Date: Fri, 30 Dec 2011 13:11:10 +0200 [thread overview]
Message-ID: <20111230111110.GC32368@x220> (raw)
In-Reply-To: <1325184068-30979-1-git-send-email-anderson.lizardo@openbossa.org>
Hi Lizardo,
On Thu, Dec 29, 2011, Anderson Lizardo wrote:
> This fix is based on commit 97046eaf3fc44b4451157b1a1bbc166ab0f4dda8.
> ---
>
> Due to some recent change, gcc 4.4.3 (from Ubuntu 10.04) started complaining
> about this code:
>
> test/hciemu.c: In function ‘hci_host_control’:
> test/hciemu.c:431: error: dereferencing pointer ‘({anonymous})’ does break
> strict-aliasing rules
> test/hciemu.c:431: note: initialized from here
>
>
> test/hciemu.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
Applied, but I had to move the stuff below --- to the actual commit
message since it's important to retain the reasons for the patches in
the git commit history.
Johan
prev parent reply other threads:[~2011-12-30 11:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 18:41 [PATCH BlueZ] Fix strict-aliasing rules handling for hciemu and IP ports Anderson Lizardo
2011-12-30 11:11 ` Johan Hedberg [this message]
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=20111230111110.GC32368@x220 \
--to=johan.hedberg@gmail.com \
--cc=anderson.lizardo@openbossa.org \
--cc=linux-bluetooth@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