From: Johan Hedberg <johan.hedberg@gmail.com>
To: Anderson Lizardo <anderson.lizardo@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFC PATCH BlueZ] doc: Revert "Small API update"
Date: Tue, 27 Mar 2012 14:59:31 +0300 [thread overview]
Message-ID: <20120327115931.GK14481@x220> (raw)
In-Reply-To: <1332778374-15320-1-git-send-email-anderson.lizardo@openbossa.org>
Hi Lizardo,
On Mon, Mar 26, 2012, Anderson Lizardo wrote:
> This reverts commit fd1ac97806d4531cb54523b3d694899afce281e7. It seems
> the "entered" param is not used anymore.
> ---
> doc/agent-api.txt | 8 +-------
> 1 files changed, 1 insertions(+), 7 deletions(-)
Why do you want to remove this? How else can we relay key press
notifications to the user? Like with your other patch the fact that some
code is not used doesn't necessarily mean that it should be removed but
that something needs to be added to make it useful.
Also, it seems we've forgotten this part from the mgmt API as there's no
event specified for it at the moment.
Johan
next prev parent reply other threads:[~2012-03-27 11:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 16:12 [RFC PATCH BlueZ] doc: Revert "Small API update" Anderson Lizardo
2012-03-27 11:59 ` Johan Hedberg [this message]
2012-03-27 12:13 ` Anderson Lizardo
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=20120327115931.GK14481@x220 \
--to=johan.hedberg@gmail.com \
--cc=anderson.lizardo@openbossa.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;
as well as URLs for NNTP newsgroup(s).