Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, gustavo@padovan.org
Subject: Re: [PATCHv2 0/4] Remove unsafe batostr
Date: Tue, 25 Sep 2012 18:27:18 +0200	[thread overview]
Message-ID: <1348590438.13371.3.camel@aeonflux> (raw)
In-Reply-To: <1348566586-28572-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>

Hi Andrei,

> Since the patch "vsprintf: add %pMR for Bluetooth MAC address" in in bluetooth-next resend the patch series.
> 
> Changes:
> 	* v2: Rebase against recent bluetooth-next.
> 
> Andrei Emeltchenko (4):
>   Bluetooth: Use %pMR in debug instead of batostr
>   Bluetooth: Use %pMR in sprintf/seq_printf  instead of batostr
>   Bluetooth: Use %pMR instead of baswap in seq_show
>   bluetooth: Remove unneeded batostr function
> 
>  include/net/bluetooth/bluetooth.h |    1 -
>  net/bluetooth/af_bluetooth.c      |   10 ++++------
>  net/bluetooth/bnep/core.c         |    3 +--
>  net/bluetooth/cmtp/core.c         |    2 +-
>  net/bluetooth/hci_conn.c          |    6 +++---
>  net/bluetooth/hci_core.c          |   22 +++++++++++-----------
>  net/bluetooth/hci_event.c         |   15 +++++++--------
>  net/bluetooth/hci_sysfs.c         |   10 +++++-----
>  net/bluetooth/hidp/core.c         |    8 ++++++--
>  net/bluetooth/l2cap_core.c        |   17 ++++++++---------
>  net/bluetooth/lib.c               |   14 --------------
>  net/bluetooth/rfcomm/core.c       |   15 +++++++--------
>  net/bluetooth/rfcomm/sock.c       |    9 ++++-----
>  net/bluetooth/rfcomm/tty.c        |    6 +++---
>  net/bluetooth/sco.c               |   12 ++++++------
>  15 files changed, 66 insertions(+), 84 deletions(-)
> 

Acked-by: Marcel Holtmann <marcel@holtmann.org>

Regards

Marcel



  parent reply	other threads:[~2012-09-25 16:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-07 15:05 [PATCHv1 0/4] Remove unsafe batostr Andrei Emeltchenko
2012-08-07 15:05 ` [PATCHv1 1/4] Bluetooth: Use %pMR BT addr print spec instead of batostr Andrei Emeltchenko
2012-08-07 15:05 ` [PATCHv1 2/4] Bluetooth: trivial: Shorten variable scope Andrei Emeltchenko
2012-08-07 15:05 ` [PATCHv1 3/4] Bluetooth: Use %pMR instead of baswap in seq_show Andrei Emeltchenko
2012-08-07 15:05 ` [PATCHv1 4/4] Bluetooth: trivial: Use preferred method for NULL check Andrei Emeltchenko
2012-08-15  4:16   ` Gustavo Padovan
2012-08-15  9:57     ` Andrei Emeltchenko
2012-08-21 17:55       ` Gustavo Padovan
2012-09-25  9:49         ` [PATCHv2 0/4] Remove unsafe batostr Andrei Emeltchenko
2012-09-25  9:49           ` [PATCHv2 1/4] Bluetooth: Use %pMR in debug instead of batostr Andrei Emeltchenko
2012-09-25  9:49           ` [PATCHv2 2/4] Bluetooth: Use %pMR in sprintf/seq_printf " Andrei Emeltchenko
2012-09-25  9:49           ` [PATCHv2 3/4] Bluetooth: Use %pMR instead of baswap in seq_show Andrei Emeltchenko
2012-09-25  9:49           ` [PATCHv2 4/4] bluetooth: Remove unneeded batostr function Andrei Emeltchenko
2012-09-25 16:27           ` Marcel Holtmann [this message]
2012-09-27 21:11           ` [PATCHv2 0/4] Remove unsafe batostr Gustavo Padovan
2012-08-07 15:45 ` [PATCHv1 " 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=1348590438.13371.3.camel@aeonflux \
    --to=marcel@holtmann.org \
    --cc=Andrei.Emeltchenko.news@gmail.com \
    --cc=gustavo@padovan.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