From: Johan Hedberg <johan.hedberg@gmail.com>
To: Jaganath K <jaganath.k.os@gmail.com>
Cc: "open list:BLUETOOTH DRIVERS" <linux-bluetooth@vger.kernel.org>
Subject: Re: [RFC 1/8] Bluetooth: Define PHY flags in hdev and set 1M as default
Date: Wed, 10 Jan 2018 11:05:41 +0200 [thread overview]
Message-ID: <20180110090541.GA17172@x1c.lan> (raw)
In-Reply-To: <CAJzH+bqDe=+ay89zPKPXcZTDnc9osC6YL_5Q0AE+7R6=QFXcjQ@mail.gmail.com>
Hi Jaganath,
On Wed, Jan 10, 2018, Jaganath K wrote:
> Any feedback on this patch set please?
In general the set looks quite good to me. This might be a good time to
send a non-RFC version of it, assuming that you haven't found any issues
with it during your testing (both with new and old controllers, I hope).
Johan
prev parent reply other threads:[~2018-01-10 9:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 6:14 [RFC 1/8] Bluetooth: Define PHY flags in hdev and set 1M as default Jaganath Kanakkassery
2017-12-20 6:14 ` [RFC 2/8] Bluetooth: Implement Get PHY Configuration mgmt command Jaganath Kanakkassery
2017-12-20 6:14 ` [RFC 3/8] Bluetooth: Implement Set PHY Confguration command Jaganath Kanakkassery
2017-12-20 6:14 ` [RFC 4/8] Bluetooth: Introduce helpers for LE set scan start and complete Jaganath Kanakkassery
2017-12-20 6:14 ` [RFC 5/8] Bluetooth: Use ext scanning if selected PHY is 2M or CODED Jaganath Kanakkassery
2017-12-20 6:14 ` [RFC 6/8] Bluetooth: Process extended ADV report event Jaganath Kanakkassery
2017-12-20 6:14 ` [RFC 7/8] Bluetooth: Introduce helpers for le conn status and complete Jaganath Kanakkassery
2017-12-20 6:14 ` [RFC 8/8] Bluetooth: Implement extended LE Connection Jaganath Kanakkassery
2018-01-10 6:57 ` [RFC 1/8] Bluetooth: Define PHY flags in hdev and set 1M as default Jaganath K
2018-01-10 9:05 ` 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=20180110090541.GA17172@x1c.lan \
--to=johan.hedberg@gmail.com \
--cc=jaganath.k.os@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;
as well as URLs for NNTP newsgroup(s).