From: "Cristian Rodríguez" <crrodriguez@opensuse.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] lib: use %m instead of strerror
Date: Mon, 24 Dec 2012 16:10:46 -0300 [thread overview]
Message-ID: <50D8A8B6.6040600@opensuse.org> (raw)
In-Reply-To: <1356369208.29264.46.camel@aeonflux>
On Mon 24 Dec 2012 02:13:28 PM CLST, Marcel Holtmann wrote:
> Hi Cristian,
>
>> Unlike strerror, %m is thread safe and we do not know
>> to what kind of program libbluetooh is being linked too.
>> ---
>> lib/sdp.c | 17 ++++++++---------
>> 1 file changed, 8 insertions(+), 9 deletions(-)
>
> patch has been applied.
>
> Regards
>
> Marcel
>
>
OK, just FYI, just checked the source code.. uclibc has to be built
with UCLIBC_HAS_PRINTF_M_SPEC=y and will be fine.
prev parent reply other threads:[~2012-12-24 19:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-24 15:25 [PATCH] lib: use %m instead of strerror Cristian Rodríguez
2012-12-24 16:49 ` Marcel Holtmann
2012-12-24 16:53 ` Cristian Rodríguez
2012-12-24 17:13 ` Marcel Holtmann
2012-12-24 19:10 ` Cristian Rodríguez [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=50D8A8B6.6040600@opensuse.org \
--to=crrodriguez@opensuse.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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;
as well as URLs for NNTP newsgroup(s).