From: Johan Hedberg <johan.hedberg@gmail.com>
To: Lukasz Rymanowski <lukasz.rymanowski@tieto.com>
Cc: linux-bluetooth@vger.kernel.org, henrik.possung@stericsson.com,
ulrik.lauren@stericsson.com
Subject: Re: [PATCH 1/4] SAP: Add support for handle ongoing call
Date: Thu, 10 Nov 2011 10:31:51 +0200 [thread overview]
Message-ID: <20111110083151.GA4484@fusion.localdomain> (raw)
In-Reply-To: <1320677803-32223-1-git-send-email-lukasz.rymanowski@tieto.com>
Hi Lukasz,
On Mon, Nov 07, 2011, Lukasz Rymanowski wrote:
> With this patch support for handling connect request
> during ongoing call is added.
>
> Change-Id: I7bd25273a33e5a14cc3698cfc560a5df47cd8f5a
> ---
> sap/sap-u8500.c | 53 ++++++++++++++++++++++++++++++++++++++++++++---------
> 1 files changed, 44 insertions(+), 9 deletions(-)
After fixing the Change-Id stuff and line widths in your commit messages
all four patches have been pushed upstream. Thanks.
Johan
prev parent reply other threads:[~2011-11-10 8:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 14:56 [PATCH 1/4] SAP: Add support for handle ongoing call Lukasz Rymanowski
2011-11-10 8:31 ` 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=20111110083151.GA4484@fusion.localdomain \
--to=johan.hedberg@gmail.com \
--cc=henrik.possung@stericsson.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=lukasz.rymanowski@tieto.com \
--cc=ulrik.lauren@stericsson.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 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).