linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gustavo Padovan <padovan@profusion.mobi>
To: Emeltchenko Andrei <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFC 2/4] Bluetooth: convert force_reliable variable to flag in l2cap chan
Date: Wed, 14 Sep 2011 01:04:33 -0300	[thread overview]
Message-ID: <20110914040433.GP16856@joana> (raw)
In-Reply-To: <1315404487-12105-2-git-send-email-Andrei.Emeltchenko.news@gmail.com>

* Emeltchenko Andrei <Andrei.Emeltchenko.news@gmail.com> [2011-09-07 17:08:05 +0300]:

> From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> 
> force_reliable variable inside l2cap_chan is a logical one and can
> be easily converted to flag
> 
> Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> ---
>  include/net/bluetooth/l2cap.h |    2 +-
>  net/bluetooth/l2cap_core.c    |    2 +-
>  net/bluetooth/l2cap_sock.c    |   13 +++++++++----
>  3 files changed, 11 insertions(+), 6 deletions(-)
> 
> diff --git a/include/net/bluetooth/l2cap.h b/include/net/bluetooth/l2cap.h
> index 4e6fb39..1302bf5 100644
> --- a/include/net/bluetooth/l2cap.h
> +++ b/include/net/bluetooth/l2cap.h
> @@ -370,7 +370,6 @@ struct l2cap_chan {
>  
>  	__u8		sec_level;
>  	__u8		role_switch;
> -	__u8		force_reliable;
>  	__u8		force_active;
>  
>  	__u8		ident;
> @@ -534,6 +533,7 @@ enum {
>  
>  /* Definitions for flags in l2cap_chan */
>  enum {
> +	FLAG_FORCE_RELIABLE,
>  	FLAG_FLUSHABLE,
>  	FLAG_EFS_ENABLE,
>  	FLAG_EXT_CTRL,
> diff --git a/net/bluetooth/l2cap_core.c b/net/bluetooth/l2cap_core.c
> index f68c88d..72caee5 100644
> --- a/net/bluetooth/l2cap_core.c
> +++ b/net/bluetooth/l2cap_core.c
> @@ -964,7 +964,7 @@ static void l2cap_conn_unreliable(struct l2cap_conn *conn, int err)
>  	list_for_each_entry(chan, &conn->chan_l, list) {
>  		struct sock *sk = chan->sk;
>  
> -		if (chan->force_reliable)
> +		if (test_bit(FLAG_FORCE_RELIABLE, &chan->flags))
>  			sk->sk_err = err;
>  	}
>  
> diff --git a/net/bluetooth/l2cap_sock.c b/net/bluetooth/l2cap_sock.c
> index 16210df..9da0ee3 100644
> --- a/net/bluetooth/l2cap_sock.c
> +++ b/net/bluetooth/l2cap_sock.c
> @@ -359,7 +359,7 @@ static int l2cap_sock_getsockopt_old(struct socket *sock, int optname, char __us
>  		if (chan->role_switch)
>  			opt |= L2CAP_LM_MASTER;
>  
> -		if (chan->force_reliable)
> +		if (test_bit(FLAG_FORCE_RELIABLE, &chan->flags))
>  			opt |= L2CAP_LM_RELIABLE;
>  
>  		if (put_user(opt, (u32 __user *) optval))
> @@ -550,7 +550,11 @@ static int l2cap_sock_setsockopt_old(struct socket *sock, int optname, char __us
>  			chan->sec_level = BT_SECURITY_HIGH;
>  
>  		chan->role_switch    = (opt & L2CAP_LM_MASTER);
> -		chan->force_reliable = (opt & L2CAP_LM_RELIABLE);
> +
> +		if (opt & L2CAP_LM_RELIABLE)
> +			set_bit(FLAG_FORCE_RELIABLE, &chan->flags);
> +		else
> +			clear_bit(FLAG_FORCE_RELIABLE, &chan->flags);
>  		break;
>  
>  	default:
> @@ -934,7 +938,8 @@ static void l2cap_sock_init(struct sock *sk, struct sock *parent)
>  		chan->tx_win = pchan->tx_win;
>  		chan->sec_level = pchan->sec_level;
>  		chan->role_switch = pchan->role_switch;
> -		chan->force_reliable = pchan->force_reliable;
> +		if (test_bit(FLAG_FORCE_RELIABLE, &pchan->flags))
> +			set_bit(FLAG_FORCE_RELIABLE, &chan->flags);

This one is also pointless.

	Gustavo

  reply	other threads:[~2011-09-14  4:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-07 14:08 [RFC 1/4] Bluetooth: convert flushable variable to flag in l2cap chan Emeltchenko Andrei
2011-09-07 14:08 ` [RFC 2/4] Bluetooth: convert force_reliable " Emeltchenko Andrei
2011-09-14  4:04   ` Gustavo Padovan [this message]
2011-09-07 14:08 ` [RFC 3/4] Bluetooth: convert force_active " Emeltchenko Andrei
2011-09-07 14:08 ` [RFC 4/4] Bluetooth: convert role_switch " Emeltchenko Andrei
2011-09-14  4:03 ` [RFC 1/4] Bluetooth: convert flushable " Gustavo Padovan
2011-09-14  4:06   ` Gustavo Padovan

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=20110914040433.GP16856@joana \
    --to=padovan@profusion.mobi \
    --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;
as well as URLs for NNTP newsgroup(s).