From: Johan Hedberg <johan.hedberg@gmail.com>
To: Emeltchenko Andrei <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCHv2 1/2] BlueZ: l2test: Use defined L2CAP extended feature mask
Date: Tue, 26 Jul 2011 11:04:00 +0300 [thread overview]
Message-ID: <20110726080400.GB9775@dell> (raw)
In-Reply-To: <1309938516-510-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>
Hi Andrei,
On Wed, Jul 06, 2011, Emeltchenko Andrei wrote:
> Sync l2cap.h from kernel concerning L2CAP extended feature mask.
> ---
> lib/l2cap.h | 12 ++++++++++++
> test/l2test.c | 20 ++++++++++----------
> 2 files changed, 22 insertions(+), 10 deletions(-)
Both patches have been applied, but before that I had to fix the commit
messages (e.g. no need for BlueZ prefix) and split this first patch into
two (the lib/l2cap.h change should be separate).
Johan
prev parent reply other threads:[~2011-07-26 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 7:48 [PATCHv2 1/2] BlueZ: l2test: Use defined L2CAP extended feature mask Emeltchenko Andrei
2011-07-06 7:48 ` [PATCHv2 2/2] Bluez: l2test: enhance L2CAP mode option Emeltchenko Andrei
2011-07-26 8:04 ` 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=20110726080400.GB9775@dell \
--to=johan.hedberg@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).