From: Johan Hedberg <johan.hedberg@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Marcel Holtmann <marcel@holtmann.org>,
Waldemar Rymarkiewicz <waldemar.rymarkiewicz@tieto.com>,
linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/2] Add RequestSecurePinCode to agent API
Date: Fri, 10 Jun 2011 10:14:44 +0900 [thread overview]
Message-ID: <20110610011444.GA13293@dell.ccr.corp.intel.com> (raw)
In-Reply-To: <20110609191833.GD2533@joana>
Hi Gustavo,
On Thu, Jun 09, 2011, Gustavo F. Padovan wrote:
> > We are getting closer to 4.100, maybe it is time to start doing the
> > transition to 5.x, which means we could start thinking on fixing the
> > current API without worrying if it breaks or not. How about that?
>
> I'm with Luiz here. Unless we want the the crazy idea of have a development
> branch we should start breaking the API someday. How about now?
I'd prefer to have mgmtops.c on par with hciops.c for BR/EDR before
doing the move to 5.x. I do prefer the RequestPinCode with the boolean
parameter option, but since it breaks the API I think it needs to wait
until we're ready to go for 5.0.
Johan
next prev parent reply other threads:[~2011-06-10 1:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 14:05 [PATCH 1/2] Add RequestSecurePinCode to agent API Waldemar Rymarkiewicz
2011-06-08 14:05 ` [PATCH 2/2] Request secure pincode from agent when necessary Waldemar Rymarkiewicz
2011-06-08 17:56 ` [PATCH 1/2] Add RequestSecurePinCode to agent API Gustavo F. Padovan
2011-06-09 8:45 ` Waldemar.Rymarkiewicz
2011-06-09 10:24 ` Marcel Holtmann
2011-06-09 12:38 ` Luiz Augusto von Dentz
2011-06-09 19:18 ` Gustavo F. Padovan
2011-06-10 0:54 ` Luiz Augusto von Dentz
2011-06-10 1:14 ` Johan Hedberg [this message]
2011-06-09 14:00 ` Waldemar.Rymarkiewicz
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=20110610011444.GA13293@dell.ccr.corp.intel.com \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=waldemar.rymarkiewicz@tieto.com \
/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).