From: Marcel Holtmann <marcel@holtmann.org>
To: "Debanjan Biswas (debiswas)" <debiswas@cisco.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Contribute: HFP: A new telephony interface component exporting all events over DBus
Date: Tue, 31 Jan 2012 23:19:15 -0800 [thread overview]
Message-ID: <1328080755.1955.237.camel@aeonflux> (raw)
In-Reply-To: <35DD4A1E71A66646BF42B14F8A62B7AC060CD6FB@XMB-BGL-419.cisco.com>
Hi Debanjan,
> I am working on a new telephony interface component of HFP & the primary purpose of the component is to export all the HFP profile events over Dbus so that any system process can retrieve the event. Further, the component will expose Remote Dbus methods that could be invoked by any process running in the system.
> Please, let me know the process to contribute this to the community.
the easiest way is to send patches here and explain what you are doing
and why. It is really hard to guess from the above what your use case or
design is in detail.
Regards
Marcel
prev parent reply other threads:[~2012-02-01 7:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 4:23 Contribute: HFP: A new telephony interface component exporting all events over DBus Debanjan Biswas (debiswas)
2012-02-01 7:19 ` Marcel Holtmann [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=1328080755.1955.237.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=debiswas@cisco.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