All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Emeltchenko Andrei <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCHv2 0/3] Ease debugging patches
Date: Fri, 17 Feb 2012 13:03:50 +0200	[thread overview]
Message-ID: <20120217110350.GA16018@x220> (raw)
In-Reply-To: <1329471657-18278-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>

Hi Andrei,

On Fri, Feb 17, 2012, Emeltchenko Andrei wrote:
> From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> 
> Increase isage of state_to_string and prefix hex numbers
> with object names.
> 
> Changes:
> 	v2: added 3rd patch, prefixing couple of hex with obj name
> 
> Andrei Emeltchenko (3):
>   Bluetooth: Move scope of state_to_string
>   Bluetooth: Use symbolic names for state in debug
>   Bluetooth: Prefix hex numbers with object name
> 
>  include/net/bluetooth/bluetooth.h |   27 +++++++++++++++++++++++++++
>  include/net/bluetooth/l2cap.h     |    3 ++-
>  net/bluetooth/hci_conn.c          |    4 ++--
>  net/bluetooth/l2cap_core.c        |   33 ++++-----------------------------
>  net/bluetooth/l2cap_sock.c        |    2 +-
>  5 files changed, 36 insertions(+), 33 deletions(-)

All three patches have been applied to my bluetooth-next tree. Thanks.

Johan

      parent reply	other threads:[~2012-02-17 11:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-17  9:40 [PATCHv2 0/3] Ease debugging patches Emeltchenko Andrei
2012-02-17  9:40 ` [PATCHv2 1/3] Bluetooth: Move scope of state_to_string Emeltchenko Andrei
2012-02-17  9:49   ` Marcel Holtmann
2012-02-17  9:40 ` [PATCHv2 2/3] Bluetooth: Use symbolic names for state in debug Emeltchenko Andrei
2012-02-17  9:50   ` Marcel Holtmann
2012-02-17  9:40 ` [PATCHv2 3/3] Bluetooth: Prefix hex numbers with object name Emeltchenko Andrei
2012-02-17  9:48   ` Marcel Holtmann
2012-02-17 11:03 ` 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=20120217110350.GA16018@x220 \
    --to=johan.hedberg@gmail.com \
    --cc=Andrei.Emeltchenko.news@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.