From: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
To: Gustavo Padovan <gustavo@padovan.org>, linux-bluetooth@vger.kernel.org
Subject: Re: [RFC 3/5] Bluetooth: Fix missing L2CAP EWS Conf parameter
Date: Thu, 29 Nov 2012 12:38:05 +0200 [thread overview]
Message-ID: <20121129103803.GB2574@aemeltch-MOBL1> (raw)
In-Reply-To: <20121129102517.GA26707@joana>
Hi Gustavo,
On Thu, Nov 29, 2012 at 08:25:17AM -0200, Gustavo Padovan wrote:
> Hi Andrei,
>
> * Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com> [2012-11-28 17:59:40 +0200]:
>
> > From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> >
> > If L2CAP_FEAT_FCS is not supported we sould miss EWS option
> > configuration because of break. Make code more readable by
> > combining FCS configuration in the single block.
> >
> > Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> > ---
> > net/bluetooth/l2cap_core.c | 30 +++++++++++++-----------------
> > 1 file changed, 13 insertions(+), 17 deletions(-)
> >
> > diff --git a/net/bluetooth/l2cap_core.c b/net/bluetooth/l2cap_core.c
> > index d8cffdb..f10e4be 100644
> > --- a/net/bluetooth/l2cap_core.c
> > +++ b/net/bluetooth/l2cap_core.c
> > @@ -3106,18 +3106,16 @@ done:
> > if (test_bit(FLAG_EFS_ENABLE, &chan->flags))
> > l2cap_add_opt_efs(&ptr, chan);
> >
> > - if (!(chan->conn->feat_mask & L2CAP_FEAT_FCS))
> > - break;
> > -
> > - if (chan->fcs == L2CAP_FCS_NONE ||
> > - test_bit(CONF_NO_FCS_RECV, &chan->conf_state)) {
> > - chan->fcs = L2CAP_FCS_NONE;
> > - l2cap_add_conf_opt(&ptr, L2CAP_CONF_FCS, 1, chan->fcs);
> > - }
> > -
> > if (test_bit(FLAG_EXT_CTRL, &chan->flags))
> > l2cap_add_conf_opt(&ptr, L2CAP_CONF_EWS, 2,
> > chan->tx_win);
> > +
> > + if (chan->conn->feat_mask & L2CAP_FEAT_FCS)
> > + if (chan->fcs == L2CAP_FCS_NONE ||
> > + test_bit(CONF_NO_FCS_RECV, &chan->conf_state)) {
> > + chan->fcs = L2CAP_FCS_NONE;
> > + l2cap_add_conf_opt(&ptr, L2CAP_CONF_FCS, 1, chan->fcs);
>
> Can you break a line here, please?
OK, will do that.
Best regards
Andrei Emeltchenko
next prev parent reply other threads:[~2012-11-29 10:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 15:59 [RFC 1/5] Bluetooth: AMP: Check that AMP is present and active Andrei Emeltchenko
2012-11-28 15:59 ` [RFC 2/5] Bluetooth: Refactor l2cap_send_disconn_req Andrei Emeltchenko
2012-11-28 15:59 ` [RFC 3/5] Bluetooth: Fix missing L2CAP EWS Conf parameter Andrei Emeltchenko
2012-11-29 10:25 ` Gustavo Padovan
2012-11-29 10:38 ` Andrei Emeltchenko [this message]
2012-11-28 15:59 ` [RFC 4/5] Bluetooth: Process receiving FCS_NONE in L2CAP Conf Rsp Andrei Emeltchenko
2012-11-29 10:27 ` Gustavo Padovan
2012-11-28 15:59 ` [RFC 5/5] Bluetooth: AMP: Mark controller radio powered down after HCIDEVDOWN Andrei Emeltchenko
2012-11-29 10:34 ` Gustavo Padovan
2012-11-29 15:46 ` [PATCHv2 1/4] Bluetooth: AMP: Check that AMP is present and active Andrei Emeltchenko
2012-11-29 15:46 ` [PATCHv2 2/4] Bluetooth: Fix missing L2CAP EWS Conf parameter Andrei Emeltchenko
2012-11-29 15:46 ` [PATCHv2 3/4] Bluetooth: Process receiving FCS_NONE in L2CAP Conf Rsp Andrei Emeltchenko
2012-11-29 15:46 ` [PATCHv2 4/4] Bluetooth: trivial: Change NO_FCS_RECV to RECV_NO_FCS Andrei Emeltchenko
2012-11-30 17:50 ` 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=20121129103803.GB2574@aemeltch-MOBL1 \
--to=andrei.emeltchenko.news@gmail.com \
--cc=gustavo@padovan.org \
--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