From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Vikrampal <vikram.pal@samsung.com>
Cc: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
Dmitry Kasatkin <d.kasatkin@samsung.com>,
cpgs@samsung.com
Subject: Re: [PATCH 0/7] L2CAP control field + AVRCP browsing PDU parsing
Date: Wed, 3 Dec 2014 10:02:12 +0200 [thread overview]
Message-ID: <CABBYNZ+ZdgJMc3crttio_oo2KbeHNxu6xB+cpsWTfLfhLjB8yQ@mail.gmail.com> (raw)
In-Reply-To: <003e01d00ec8$0b325380$2196fa80$@samsung.com>
Hi Vikram,
On Wed, Dec 3, 2014 at 9:08 AM, Vikrampal <vikram.pal@samsung.com> wrote:
> Hi Luiz,
>
>> -----Original Message-----
>> From: Luiz Augusto von Dentz [mailto:luiz.dentz@gmail.com]
>> Sent: Friday, November 28, 2014 2:07 PM
>> To: Vikrampal Yadav
>> Cc: linux-bluetooth@vger.kernel.org; Dmitry Kasatkin; cpgs@samsung.com
>> Subject: Re: [PATCH 0/7] L2CAP control field + AVRCP browsing PDU parsing
>>
>> Hi Vikram,
>>
>> On Fri, Nov 21, 2014 at 3:47 PM, Vikrampal Yadav
>> <vikram.pal@samsung.com> wrote:
>> > Support for ERTM control bytes adjustment, parsing L2CAP extended
>> > control field and AVRCP SetBrowsedPlayer added in Bluetooth monitor.
>> >
>> > Vikrampal Yadav (7):
>> > monitor: Adjust for ERTM control bytes
>> > monitor: Make the parameter name generic
>> > monitor: Add functionality to store extented control in DB
>> > monitor: Extract extended L2CAP extended control field
>> > monitor: Add support for parsing L2CAP extended control field
>> > monitor: Add support for parsing L2CAP control field
>> > monitor: Add AVRCP SetBrowsedPlayer support
>> >
>> > monitor/avctp.c | 86 +++++++++++++++++++- monitor/l2cap.c | 242
>> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++--
>> > 2 files changed, 322 insertions(+), 6 deletions(-)
>> >
>> > --
>> > 1.9.1
>>
>> Sorry for the delay, this one got lost in my inbox, most patches seems to be
>> missing the output they generate, could you please add it.
>
> Most patches in this series are helper patches for the last patch in this series.
> The final patch actually prints the output which shows the work done by
> Other patches.
Actually from patch 4/7 onward they all print different output and I
remember commenting before that I want to see then in the patches so
we can avoid format errors, typos etc.
--
Luiz Augusto von Dentz
next prev parent reply other threads:[~2014-12-03 8:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 13:47 [PATCH 0/7] L2CAP control field + AVRCP browsing PDU parsing Vikrampal Yadav
2014-11-21 13:47 ` [PATCH 1/7] monitor: Adjust for ERTM control bytes Vikrampal Yadav
2014-11-28 8:37 ` Luiz Augusto von Dentz
2014-12-03 7:05 ` Vikrampal
2014-12-03 8:20 ` Luiz Augusto von Dentz
2014-11-21 13:47 ` [PATCH 2/7] monitor: Make the parameter name generic Vikrampal Yadav
2014-11-21 13:47 ` [PATCH 3/7] monitor: Add functionality to store extented control in DB Vikrampal Yadav
2014-11-21 13:47 ` [PATCH 4/7] monitor: Extract extended L2CAP extended control field Vikrampal Yadav
2014-11-21 13:47 ` [PATCH 5/7] monitor: Add support for parsing " Vikrampal Yadav
2014-11-21 13:47 ` [PATCH 6/7] monitor: Add support for parsing L2CAP " Vikrampal Yadav
2014-11-21 13:47 ` [PATCH 7/7] monitor: Add AVRCP SetBrowsedPlayer support Vikrampal Yadav
2014-11-28 8:37 ` [PATCH 0/7] L2CAP control field + AVRCP browsing PDU parsing Luiz Augusto von Dentz
2014-12-03 7:08 ` Vikrampal
2014-12-03 8:02 ` Luiz Augusto von Dentz [this message]
2014-12-03 8:57 ` Vikrampal
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=CABBYNZ+ZdgJMc3crttio_oo2KbeHNxu6xB+cpsWTfLfhLjB8yQ@mail.gmail.com \
--to=luiz.dentz@gmail.com \
--cc=cpgs@samsung.com \
--cc=d.kasatkin@samsung.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=vikram.pal@samsung.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.