From: Marcel Holtmann <marcel@holtmann.org>
To: Ulisses Furquim <ulisses@profusion.mobi>
Cc: David Herrmann <dh.herrmann@googlemail.com>,
linux-bluetooth@vger.kernel.org, gustavo@padovan.org
Subject: Re: [PATCH 3/3] Bluetooth: Remove batostr()
Date: Tue, 08 May 2012 07:54:40 -0700 [thread overview]
Message-ID: <1336488880.5970.149.camel@aeonflux> (raw)
In-Reply-To: <CAA37ikZW1H1zfPr8d5uonpY0SEZk=dbDQ+XsYhOytXg4ExuLAA@mail.gmail.com>
Hi Ulisses,
> > batostr() is not used anywhere and I don't see any reason why we should
> > keep it. Use ba2str() instead.
> >
> > Signed-off-by: David Herrmann <dh.herrmann@googlemail.com>
> > ---
> > include/net/bluetooth/bluetooth.h | 1 -
> > net/bluetooth/lib.c | 14 --------------
> > 2 files changed, 15 deletions(-)
>
> The patchset looks good to me. I'm also not sure we need another
> specifier for snprintf().
>
> Given we had static buffers instead of allocating them in the stack
> every time it'd be good to hear from Marcel if we had a reason and if
> it's still valid. IMO we don't have problems with stack usage in our
> code paths now but I haven't actually checked it.
that code is most likely 11+ years old. It is actually not from me. So
if you wanna know why, you need to track down Max.
Using %pM and baswap seems to be the best approach for fixing this right
now. However I am not against introducing a snprintf modifier for
Bluetooth addresses.
Regards
Marcel
next prev parent reply other threads:[~2012-05-08 14:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 13:28 [PATCH 1/3] Bluetooth: Introduce ba2str() David Herrmann
2012-05-08 13:28 ` [PATCH 2/3] Bluetooth: Replace unsafe batostr() calls with ba2str() David Herrmann
2012-05-08 13:49 ` Andrei Emeltchenko
2012-05-08 14:02 ` David Herrmann
2012-05-08 14:34 ` Andrei Emeltchenko
2012-05-08 13:28 ` [PATCH 3/3] Bluetooth: Remove batostr() David Herrmann
2012-05-08 14:30 ` Ulisses Furquim
2012-05-08 14:54 ` Marcel Holtmann [this message]
2012-05-08 18:11 ` Ulisses Furquim
2012-05-09 9:02 ` Andrei Emeltchenko
2012-05-09 11:17 ` Ulisses Furquim
2012-05-09 13:10 ` Gustavo Padovan
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=1336488880.5970.149.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=dh.herrmann@googlemail.com \
--cc=gustavo@padovan.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ulisses@profusion.mobi \
/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