From: Marcel Holtmann <marcel@holtmann.org>
To: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCHv3] Bluetooth: Define L2CAP conf continuation flag
Date: Wed, 23 May 2012 14:46:35 +0200 [thread overview]
Message-ID: <1337777195.15105.78.camel@aeonflux> (raw)
In-Reply-To: <1337777047-13515-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>
Hi Andrei,
> Define Continuation flag which the only flag used from Flags field
> in L2CAP Configuration Request and Response.
>
> Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> ---
> include/net/bluetooth/l2cap.h | 3 +++
> net/bluetooth/l2cap_core.c | 10 +++++-----
> 2 files changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/include/net/bluetooth/l2cap.h b/include/net/bluetooth/l2cap.h
> index 7bc4019..5de6912 100644
> --- a/include/net/bluetooth/l2cap.h
> +++ b/include/net/bluetooth/l2cap.h
> @@ -271,6 +271,9 @@ struct l2cap_conf_rsp {
> #define L2CAP_CONF_PENDING 0x0004
> #define L2CAP_CONF_EFS_REJECT 0x0005
>
> +/* configuration req/rsp continuation flag */
> +#define L2CAP_CONF_FLAG_CONTINUATION 1
> +
I changed the 1 into 0x0001 and then applied your patch to
bluetooth-next tree.
Regards
Marcel
next prev parent reply other threads:[~2012-05-23 12:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 8:31 [PATCH trivial 1/4] Bluetooth: Use defined link key size Andrei Emeltchenko
2012-05-23 8:31 ` [PATCH trivial 2/4] Bluetooth: Define L2CAP conf continuation flag Andrei Emeltchenko
2012-05-23 11:05 ` Marcel Holtmann
2012-05-23 12:44 ` [PATCHv3] " Andrei Emeltchenko
2012-05-23 12:46 ` Marcel Holtmann [this message]
2012-05-23 8:31 ` [PATCH trivial 3/4] Bluetooth: Preserve flags values Andrei Emeltchenko
2012-05-23 11:07 ` Marcel Holtmann
2012-05-23 8:31 ` [PATCH trivial 4/4] Bluetooth: trivial: Remove empty line Andrei Emeltchenko
2012-05-23 11:08 ` Marcel Holtmann
2012-05-23 11:04 ` [PATCH trivial 1/4] Bluetooth: Use defined link key size Marcel Holtmann
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=1337777195.15105.78.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=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