All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gustavo F. Padovan" <padovan@profusion.mobi>
To: Andrei Emeltchenko <andrei.emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFCv1 3/3] Bluetooth: delete hanging L2CAP channel
Date: Fri, 25 Mar 2011 09:35:43 -0300	[thread overview]
Message-ID: <20110325123458.GA2596@joana> (raw)
In-Reply-To: <AANLkTim2_owHJ9NT4B7u484D1itkuEmGUzdp1wxgaZTi@mail.gmail.com>

Hi Andrei,

* Andrei Emeltchenko <andrei.emeltchenko.news@gmail.com> [2011-03-25 10:57:52 +0200]:

> Hi Gustavo,
> 
> On Thu, Mar 24, 2011 at 9:12 PM, Gustavo F. Padovan
> <padovan@profusion.mobi> wrote:
> > Hi Andrei,
> >
> > * Emeltchenko Andrei <Andrei.Emeltchenko.news@gmail.com> [2011-03-24 17:16:08 +0200]:
> >
> >> From: Andrei Emeltchenko <andrei.emeltchenko@nokia.com>
> >>
> >> Sometimes L2CAP connection remains hanging. Make sure that
> >> L2CAP channel is deleted.
> >>
> >> Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@nokia.com>
> >> ---
> >>  net/bluetooth/l2cap_sock.c |    5 +++--
> >>  1 files changed, 3 insertions(+), 2 deletions(-)
> >
> > This one is applied. Thanks.
> 
> Where it is applied? Cannot find it here:

I applied it to bluetooth-2.6 as it is a bug fix.

-- 
Gustavo F. Padovan
http://profusion.mobi

      reply	other threads:[~2011-03-25 12:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-24 15:16 [RFCv1 0/3] Set of patches fixing kernel crash Emeltchenko Andrei
2011-03-24 15:16 ` [RFCv1 1/3] Bluetooth: check info_rsp ident and states Emeltchenko Andrei
2011-03-24 19:11   ` Gustavo F. Padovan
2011-03-24 15:16 ` [RFCv1 2/3] Bluetooth: remove duplicated code Emeltchenko Andrei
2011-03-24 18:57   ` Gustavo F. Padovan
2011-03-25  9:35     ` Andrei Emeltchenko
2011-03-24 15:16 ` [RFCv1 3/3] Bluetooth: delete hanging L2CAP channel Emeltchenko Andrei
2011-03-24 19:12   ` Gustavo F. Padovan
2011-03-25  8:57     ` Andrei Emeltchenko
2011-03-25 12:35       ` Gustavo F. 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=20110325123458.GA2596@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.