From: Marcel Holtmann <marcel@holtmann.org>
To: "Frédéric Danis" <frederic.danis@linux.intel.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2] hciconfig: Remove putkey command
Date: Wed, 05 Dec 2012 12:06:46 +0100 [thread overview]
Message-ID: <1354705606.1815.6.camel@aeonflux> (raw)
In-Reply-To: <1354705348-28264-1-git-send-email-frederic.danis@linux.intel.com>
Hi Fred,
> tools/hciconfig.c | 64 -----------------------------------------------------
> 1 file changed, 64 deletions(-)
that command does have a manpage entry.
Regards
Marcel
next prev parent reply other threads:[~2012-12-05 11:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 10:20 [PATCH] hciconfig: Retrieve linkey from device info file Frédéric Danis
2012-12-05 10:33 ` Marcel Holtmann
2012-12-05 11:02 ` [PATCH v2] hciconfig: Remove putkey command Frédéric Danis
2012-12-05 11:06 ` Marcel Holtmann [this message]
2012-12-05 11:26 ` Johan Hedberg
2012-12-05 11:43 ` [PATCH v3] " Frédéric Danis
2012-12-05 15:25 ` Johan Hedberg
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=1354705606.1815.6.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=frederic.danis@linux.intel.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;
as well as URLs for NNTP newsgroup(s).