All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Szymon Janc <szymon.janc@tieto.com>
Cc: linux-bluetooth@vger.kernel.org, kanak.gupta@stericsson.com
Subject: Re: [PATCH v2 0/5] Some ERTM improvements
Date: Wed, 11 Jan 2012 13:21:54 +0200	[thread overview]
Message-ID: <20120111112154.GA23277@x220> (raw)
In-Reply-To: <1326275989-32226-1-git-send-email-szymon.janc@tieto.com>

Hi Szymon,

On Wed, Jan 11, 2012, Szymon Janc wrote:
> No code changes since v1.
> Only improved commits messages as requested by Marcel.
> 
> Szymon Janc (5):
>   Bluetooth: Make l2cap_clear_timer return if timer was running or not
>   Bluetooth: Set P-bit for SREJ frame only if there are I-frames to ack
>   Bluetooth: Clear ack_timer when sending ack
>   Bluetooth: Don't send RNR immediately when entering local busy
>   Bluetooth: Drop L2CAP chan reference if ERTM ack_timer fired
> 
>  include/net/bluetooth/l2cap.h |    9 +++++++--
>  net/bluetooth/l2cap_core.c    |   33 ++++++++++++++++++---------------
>  2 files changed, 25 insertions(+), 17 deletions(-)

All five patches have been applied to my bluetooth-next tree. Thanks.

Johan

      parent reply	other threads:[~2012-01-11 11:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-11  9:59 [PATCH v2 0/5] Some ERTM improvements Szymon Janc
2012-01-11  9:59 ` [PATCH v2 1/5] Bluetooth: Make l2cap_clear_timer return if timer was running or not Szymon Janc
2012-01-11  9:59 ` [PATCH v2 2/5] Bluetooth: Set P-bit for SREJ frame only if there are I-frames to ack Szymon Janc
2012-01-11  9:59 ` [PATCH v2 3/5] Bluetooth: Clear ack_timer when sending ack Szymon Janc
2012-01-11  9:59 ` [PATCH v2 4/5] Bluetooth: Don't send RNR immediately when entering local busy Szymon Janc
2012-01-11  9:59 ` [PATCH v2 5/5] Bluetooth: Drop L2CAP chan reference if ERTM ack_timer fired Szymon Janc
2012-01-11 10:28 ` [PATCH v2 0/5] Some ERTM improvements Marcel Holtmann
2012-01-11 11:21 ` Johan Hedberg [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=20120111112154.GA23277@x220 \
    --to=johan.hedberg@gmail.com \
    --cc=kanak.gupta@stericsson.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=szymon.janc@tieto.com \
    /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.