From: Marcel Holtmann <marcel@holtmann.org>
To: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Remove unneeded zero initialization
Date: Wed, 28 Mar 2012 14:46:24 +0200 [thread overview]
Message-ID: <1332938784.1870.166.camel@aeonflux> (raw)
In-Reply-To: <1332935794-15319-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>
Hi Andrei,
> Remove zero initialization since channel is allocated with kzalloc
> in l2cap_chan_create.
>
> Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> ---
> net/bluetooth/l2cap_sock.c | 3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
>
> diff --git a/net/bluetooth/l2cap_sock.c b/net/bluetooth/l2cap_sock.c
> index 53e563f..4e73b41 100644
> --- a/net/bluetooth/l2cap_sock.c
> +++ b/net/bluetooth/l2cap_sock.c
> @@ -999,7 +999,7 @@ static void l2cap_sock_init(struct sock *sk, struct sock *parent)
> }
>
> chan->imtu = L2CAP_DEFAULT_MTU;
> - chan->omtu = 0;
> +
while technically not needed. This seems like a good idea to keep from a
visual point of view.
> if (!disable_ertm && sk->sk_type == SOCK_STREAM) {
> chan->mode = L2CAP_MODE_ERTM;
> set_bit(CONF_STATE2_DEVICE, &chan->conf_state);
> @@ -1011,7 +1011,6 @@ static void l2cap_sock_init(struct sock *sk, struct sock *parent)
> chan->tx_win = L2CAP_DEFAULT_TX_WINDOW;
> chan->tx_win_max = L2CAP_DEFAULT_TX_WINDOW;
> chan->sec_level = BT_SECURITY_LOW;
> - chan->flags = 0;
This one can be removed indeed.
> set_bit(FLAG_FORCE_ACTIVE, &chan->flags);
> }
>
Regards
Marcel
next prev parent reply other threads:[~2012-03-28 12:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 11:56 [PATCH] Bluetooth: Remove unneeded zero initialization Andrei Emeltchenko
2012-03-28 12:46 ` Marcel Holtmann [this message]
2012-03-28 13:06 ` Andrei Emeltchenko
2012-03-28 14:05 ` Marcel Holtmann
2012-03-28 14:33 ` 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=1332938784.1870.166.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;
as well as URLs for NNTP newsgroup(s).