All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Peter Krystad <pkrystad@codeaurora.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v4 1/5] Add L2CAP Create/Move Channel definitions
Date: Wed, 29 Feb 2012 19:34:37 -0600	[thread overview]
Message-ID: <20120301013437.GA26097@x220> (raw)
In-Reply-To: <1329332655-27394-2-git-send-email-pkrystad@codeaurora.org>

Hi Peter,

On Wed, Feb 15, 2012, Peter Krystad wrote:
> ---
>  lib/l2cap.h |   45 +++++++++++++++++++++++++++++++++++++++++++++
>  1 files changed, 45 insertions(+), 0 deletions(-)

I've applied this one to both bluez-hcidump.git as well as bluez.git
(after adding a lib: prefix that should be used for all lib patches).

Since any patches to lib/* should be appliable to both hcidump and bluez
please don't mix Makefile.am changes into them. Once you've split those
into separate patches I can apply them as well as the rest of this set.
Thanks.

Johan

  reply	other threads:[~2012-03-01  1:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-15 19:04 [PATCH v4 0/5] Add parsing of BT 3.0+HS signals Peter Krystad
2012-02-15 19:04 ` [PATCH v4 1/5] Add L2CAP Create/Move Channel definitions Peter Krystad
2012-03-01  1:34   ` Johan Hedberg [this message]
2012-02-15 19:04 ` [PATCH v4 2/5] Add A2MP definitions Peter Krystad
2012-02-15 19:04 ` [PATCH v4 3/5] Add parsing of L2CAP Create/Move Channel signals Peter Krystad
2012-02-15 19:04 ` [PATCH v4 4/5] Add parsing of A2MP signals Peter Krystad
2012-02-15 19:04 ` [PATCH v4 5/5] Minor indentation cleanup and fix display of physical link key Peter Krystad
  -- strict thread matches above, loose matches on Subject: below --
2012-02-15  1:09 [PATCH v4 0/5] Add parsing of BT 3.0+HS signals y
2012-02-15  1:09 ` [PATCH v4 1/5] Add L2CAP Create/Move Channel definitions y

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=20120301013437.GA26097@x220 \
    --to=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=pkrystad@codeaurora.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.