From: event <event.riga@gmail.com>
To: Zhao Forrest <forrest.zhao@gmail.com>
Cc: Michele Noberasco <michele.noberasco@tiscali.it>,
BlueZ development <linux-bluetooth@vger.kernel.org>,
Marcel Holtmann <marcel@holtmann.org>
Subject: Re: [PATCH] BlueZ support for audio gateway role (HFP/HSP)
Date: Mon, 9 Feb 2009 11:49:46 +0200 [thread overview]
Message-ID: <664d43d60902090149gf960fbfg99384adb3f26f0f9@mail.gmail.com> (raw)
In-Reply-To: <ac8af0be0902082138u9d3eb63hae9c5739b198072b@mail.gmail.com>
On Mon, Feb 9, 2009 at 07:38, Zhao Forrest <forrest.zhao@gmail.com> wrote:
>>>>>
>>>>>
>>>>
>>>> Hello Michele,
>>>>
>>>> Saying honestly - no :). I've already implemented the functionality
>>>> found in your patch. But thank you anyhow.
>>>>
>>> Event,
>>> What's the current status of your patch? Is it still pending on main BlueZ
>>> developer's review? If this is the case I think that you split the big
>>> patch into
>>> small pieces could make the code review process more smooth :)
>>>
>>> Thanks,
>>> Forrest
>>>
>> Hello Zhao,
>>
>> Unfortunately, I don't have time currently to work on this.
> Do you mind if we pick up your patch and divide it into smaller pieces
> to try to push
> it into BlueZ upstream?
>
> Thanks,
> Forrest
>
Hello Forrest,
Yes, I would be pleased if you'll take it :)
Vale,
Leonid Movshovich
prev parent reply other threads:[~2009-02-09 9:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 16:43 [PATCH] BlueZ support for audio gateway role (HFP/HSP) Michele Noberasco
2009-01-23 7:34 ` event
2009-01-23 8:32 ` Michele Noberasco
2009-01-28 5:54 ` Marcel Holtmann
2009-01-29 8:34 ` Michele Noberasco
2009-01-29 8:46 ` event
2009-02-05 5:06 ` Zhao Forrest
2009-02-05 7:22 ` event
2009-02-09 5:38 ` Zhao Forrest
2009-02-09 9:49 ` event [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=664d43d60902090149gf960fbfg99384adb3f26f0f9@mail.gmail.com \
--to=event.riga@gmail.com \
--cc=forrest.zhao@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=michele.noberasco@tiscali.it \
/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