Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting correct length for BTSTACK_EVENT_STATE event. #1

Merged
merged 1 commit into from
Mar 30, 2015

Conversation

peteblois
Copy link

The second byte of the data is the length of the remaining data (in this case the HCI_STATE_WORKING byte). This was passing 0 indicating that there was no data when in fact there was.

The second byte of the data is the length of the remaining data (in this case the HCI_STATE_WORKING byte). This was passing 0 indicating that there was no data when in fact there was.
mringwal added a commit that referenced this pull request Mar 30, 2015
Setting correct length for BTSTACK_EVENT_STATE event.
@mringwal mringwal merged commit a3a35d6 into bluekitchen:master Mar 30, 2015
@mringwal
Copy link
Member

Thanks!

@peteblois
Copy link
Author

No problem at all, welcome to Github! :)

On Mon, Mar 30, 2015 at 1:35 PM, Matthias Ringwald <notifications@github.com

wrote:

Thanks!


Reply to this email directly or view it on GitHub
#1 (comment).

@swfredrik swfredrik mentioned this pull request Jul 13, 2015
mringwal added a commit that referenced this pull request Jan 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants