From: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH hcidump 1/2] lib: Correct length name in write assoc struct
Date: Thu, 19 Jul 2012 12:08:24 +0300 [thread overview]
Message-ID: <1342688905-31924-1-git-send-email-Andrei.Emeltchenko.news@gmail.com> (raw)
From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
Correct name from assoc_length to remaining_length.
---
lib/hci.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/hci.h b/lib/hci.h
index b68dbc2..3dbb221 100644
--- a/lib/hci.h
+++ b/lib/hci.h
@@ -1408,7 +1408,7 @@ typedef struct {
typedef struct {
uint8_t handle;
uint16_t length_so_far;
- uint16_t assoc_length;
+ uint16_t remaining_length;
uint8_t fragment[HCI_MAX_NAME_LENGTH];
} __attribute__ ((packed)) write_remote_amp_assoc_cp;
#define WRITE_REMOTE_AMP_ASSOC_CP_SIZE 253
--
1.7.9.5
next reply other threads:[~2012-07-19 9:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 9:08 Andrei Emeltchenko [this message]
2012-07-19 9:08 ` [PATCH hcidump 2/2] Add decoding AMP Assoc data in write_remote_amp_assoc Andrei Emeltchenko
2012-07-19 12:16 ` [PATCH hcidump 1/2] lib: Correct length name in write assoc struct 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=1342688905-31924-1-git-send-email-Andrei.Emeltchenko.news@gmail.com \
--to=andrei.emeltchenko.news@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).