linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: "Frédéric Danis" <frederic.danis@linux.intel.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFC v4 0/6] Add org.bluez.Telephony interface
Date: Mon, 12 Dec 2011 13:03:08 +0200	[thread overview]
Message-ID: <20111212110308.GA12769@x220> (raw)
In-Reply-To: <1323686954-11899-1-git-send-email-frederic.danis@linux.intel.com>

Hi Frédéric,

On Mon, Dec 12, 2011, Frédéric Danis wrote:
> First patch add the new org.bluez.Telephony interface and remove
> functions related to AT parsing from audio/headset.c.
> 
> Second, third and fourth patches remove the telephony drivers (dummy,
> maemo5, maemo6 and ofono), functions used by telephony drivers and no
> more needed methods of org.bluez.Headset interface.
> 
> Fifth patch move the HS/HF AG rfcomm servers from audio/manager.c to
> audio/telephony.c.
> Rfcomm server for a specific profile is only started (and the related
> sdp records advertised) when an agent register for it.
> 
> Sixth patch passes MediaTransport path to the agent during
> NewConnection mehod call. So, telephony agent will be able to set NREC
> and ringtone, which can in turn notify Pulse Audio of property changed.

Could you please add these descriptions (and possibly even more thorough
explanations) to the commit messages of each patch. We really should try
to avoid one-line commit messages for all but the most trivial patches
(and even for those I wont complain if you have longer explanations).
Remember that the summary line should be a very short summary of *what*
the patch does whereas the rest of the message can elaborate on it (if
necessary) but more importantly explain *why* the patch was needed and
how it goes about solving some issue.

Johan

  parent reply	other threads:[~2011-12-12 11:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-12 10:49 [RFC v4 0/6] Add org.bluez.Telephony interface Frédéric Danis
2011-12-12 10:49 ` [RFC v4 1/6] audio: Move tel drivers to DBus interface Frédéric Danis
2011-12-12 10:49 ` [RFC v4 2/6] audio: Remove tel drivers Frédéric Danis
2011-12-12 10:49 ` [RFC v4 3/6] audio: Remove maemo5 tel driver Frédéric Danis
2011-12-12 10:49 ` [RFC v4 4/6] audio: Remove maemo6 " Frédéric Danis
2011-12-12 10:49 ` [RFC v4 5/6] audio: Move HFP/HSP AG servers to telephony.c Frédéric Danis
2011-12-12 10:49 ` [RFC v4 6/6] audio: Send transport path to telephony agent Frédéric Danis
2011-12-12 11:03 ` Johan Hedberg [this message]
2011-12-12 21:24   ` [RFC v4 0/6] Add org.bluez.Telephony interface Dmitriy Paliy

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=20111212110308.GA12769@x220 \
    --to=johan.hedberg@gmail.com \
    --cc=frederic.danis@linux.intel.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).