Linux bluetooth development
 help / color / mirror / Atom feed
From: Emeltchenko Andrei <Andrei.Emeltchenko.news@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCHv4 2/3] Bluetooth: EFS: parse L2CAP config response
Date: Wed, 2 Nov 2011 09:51:28 +0200	[thread overview]
Message-ID: <20111102075125.GA12653@aemeltch-MOBL1> (raw)
In-Reply-To: <20111017201008.GD2631@joana>

Hi Gustavo,

On Mon, Oct 17, 2011 at 06:10:08PM -0200, Gustavo Padovan wrote:
> Hi Andrei,
> 
> * Emeltchenko Andrei <Andrei.Emeltchenko.news@gmail.com> [2011-10-17 14:35:31 +0300]:
> 
> > From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> > 
> > Add parsing Extended Flow Specification in L2CAP Config Response.
> > Based upon haijun.liu <haijun.liu@atheros.com> series of patches
> > (sent Sun, 22 Aug 2010)
> > 
> > Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> > ---
> >  net/bluetooth/l2cap_core.c |   24 ++++++++++++++++++++++++
> >  1 files changed, 24 insertions(+), 0 deletions(-)
> 
> Applied, thanks.

Was this patch actually applied?

Best regards 
Andrei Emeltchenko 

  reply	other threads:[~2011-11-02  7:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-17 11:35 [PATCHv4 0/3] EFS: last chunks Emeltchenko Andrei
2011-10-17 11:35 ` [PATCHv4 1/3] Bluetooth: EFS: parse L2CAP config request Emeltchenko Andrei
2011-10-17 20:09   ` Gustavo Padovan
2011-10-17 11:35 ` [PATCHv4 2/3] Bluetooth: EFS: parse L2CAP config response Emeltchenko Andrei
2011-10-17 20:10   ` Gustavo Padovan
2011-11-02  7:51     ` Emeltchenko Andrei [this message]
2011-11-03 14:10       ` Gustavo Padovan
2011-11-07 12:23         ` Emeltchenko Andrei
2011-10-17 11:35 ` [PATCHv4 3/3] Bluetooth: EFS: implement L2CAP config pending state Emeltchenko Andrei
2011-11-01 16:07   ` 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=20111102075125.GA12653@aemeltch-MOBL1 \
    --to=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