From: Marcel Holtmann <marcel@holtmann.org>
To: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 2/2] Bluetooth: Fix debug printing unallocated name
Date: Mon, 16 Apr 2012 15:41:55 +0200 [thread overview]
Message-ID: <1334583715.16897.176.camel@aeonflux> (raw)
In-Reply-To: <1334583124-15134-2-git-send-email-Andrei.Emeltchenko.news@gmail.com>
Hi Andrei,
> It does make sense to print hdev name after allocation.
>
> Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> ---
> net/bluetooth/hci_core.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
patch has been applied to bluetooth-next tree.
Regards
Marcel
next prev parent reply other threads:[~2012-04-16 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 13:32 [PATCH 1/2] Bluetooth: trivial: Remove empty line Andrei Emeltchenko
2012-04-16 13:32 ` [PATCH 2/2] Bluetooth: Fix debug printing unallocated name Andrei Emeltchenko
2012-04-16 13:41 ` Marcel Holtmann [this message]
2012-04-16 13:39 ` [PATCH 1/2] Bluetooth: trivial: Remove empty line 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=1334583715.16897.176.camel@aeonflux \
--to=marcel@holtmann.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox