From: Vinicius Costa Gomes <vinicius.gomes@openbossa.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "Elvis Pfützenreuter" <epx@signove.com>,
"Anderson Briglia" <anderson.briglia@openbossa.org>,
linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Remove btio.c compilation warning
Date: Thu, 5 May 2011 11:05:31 -0300 [thread overview]
Message-ID: <20110505140531.GA27568@piper> (raw)
In-Reply-To: <BANLkTikLnb229tLvdeeWMnfqkqdSAva1bQ@mail.gmail.com>
Hi Luiz,
On 11:05 Thu 05 May, Luiz Augusto von Dentz wrote:
[snip]
>
> I don't see why it would be ubuntu specific, this seems to be some
> kind of regression/'feature' with gcc 4.5.
Yeah, I really believe this is the case. I have gcc 4.5.2 here, that
would be the version as in Natty, and I don't encounter that problem.
The only difference that I could find is that Ubuntu ships gcc with
a .diff.gz of 1.3MB ;-)
But back to the topic at hand, I agree that the patch should be applied,
Ubuntu is used by many developers and BlueZ should be kept clean of
warnings.
>
> --
> Luiz Augusto von Dentz
> Computer Engineer
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Cheers,
--
Vinicius
next prev parent reply other threads:[~2011-05-05 14:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 20:43 [PATCH] Remove btio.c compilation warning anderson.briglia
2011-05-02 20:56 ` Antonio Ospite
2011-05-02 21:15 ` Johan Hedberg
2011-05-02 21:23 ` Elvis Pfützenreuter
2011-05-02 21:33 ` Anderson Briglia
2011-05-02 21:47 ` Gustavo F. Padovan
2011-05-04 21:39 ` Johan Hedberg
2011-05-04 23:09 ` Anderson Briglia
2011-05-04 23:23 ` Elvis Pfützenreuter
2011-05-05 8:05 ` Luiz Augusto von Dentz
2011-05-05 14:05 ` Vinicius Costa Gomes [this message]
2011-05-05 14:30 ` Luiz Augusto von Dentz
2011-05-05 18:51 ` Anderson Briglia
2011-05-05 19:01 ` Bastien Nocera
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=20110505140531.GA27568@piper \
--to=vinicius.gomes@openbossa.org \
--cc=anderson.briglia@openbossa.org \
--cc=epx@signove.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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;
as well as URLs for NNTP newsgroup(s).