Linux bluetooth development
 help / color / mirror / Atom feed
From: Gustavo Padovan <gustavo@padovan.org>
To: Dean Jenkins <Dean_Jenkins@mentor.com>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org
Subject: Re: [PATCH v2 6/6] Bluetooth: Remove redundant RFCOMM BT_CLOSED settings
Date: Thu, 28 Feb 2013 12:36:42 -0300	[thread overview]
Message-ID: <20130228153642.GA27428@joana> (raw)
In-Reply-To: <1362061318-30580-7-git-send-email-Dean_Jenkins@mentor.com>

Hi Dean,

* Dean Jenkins <Dean_Jenkins@mentor.com> [2013-02-28 14:21:58 +0000]:

> rfcomm_session_close() sets the RFCOMM session state to BT_CLOSED.
> However, in multiple places immediately before the function is
> called, the RFCOMM session is set to BT_CLOSED. Therefore,
> remove these unnecessary state settings.
> 
> Signed-off-by: Dean Jenkins <Dean_Jenkins@mentor.com>
> Acked-by: Marcel Holtmann <marcel@holtmann.org>
> ---
>  net/bluetooth/rfcomm/core.c |    7 ++-----
>  1 file changed, 2 insertions(+), 5 deletions(-)

Patches has been applied to bluetooth-next. Thanks for the nice work in
RFCOMM.

	Gustavo

      reply	other threads:[~2013-02-28 15:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-28 14:21 [PATCH v2 0/6] Bluetooth: Rework the RFCOMM session refcnt Dean Jenkins
2013-02-28 14:21 ` [PATCH v2 1/6] Bluetooth: Avoid rfcomm_session_timeout using freed session Dean Jenkins
2013-02-28 14:21 ` [PATCH v2 2/6] Bluetooth: Check rfcomm session and DLC exists on socket close Dean Jenkins
2013-02-28 14:21 ` [PATCH v2 3/6] Bluetooth: Return RFCOMM session ptrs to avoid freed session Dean Jenkins
2013-02-28 14:21 ` [PATCH v2 4/6] Bluetooth: Remove RFCOMM session refcnt Dean Jenkins
2013-02-28 14:21 ` [PATCH v2 5/6] Bluetooth: Remove redundant call to rfcomm_send_disc Dean Jenkins
2013-02-28 14:21 ` [PATCH v2 6/6] Bluetooth: Remove redundant RFCOMM BT_CLOSED settings Dean Jenkins
2013-02-28 15:36   ` Gustavo Padovan [this message]

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=20130228153642.GA27428@joana \
    --to=gustavo@padovan.org \
    --cc=Dean_Jenkins@mentor.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.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