From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: [PATCH] huawei: fix AT^DDSETEX=2 timing
Date: Fri, 23 Mar 2012 12:13:21 -0700 [thread overview]
Message-ID: <1332530001.1870.61.camel@aeonflux> (raw)
In-Reply-To: <1331397973-28076-2-git-send-email-devel@jlranta.com>
[-- Attachment #1: Type: text/plain, Size: 280 bytes --]
Hi Jarkko,
> ---
> drivers/huaweimodem/voicecall.c | 12 +++++++++---
> 1 file changed, 9 insertions(+), 3 deletions(-)
can I get a patch where the long explanation summary is actually the
commit message. I want this recorded in the git log.
Regards
Marcel
next prev parent reply other threads:[~2012-03-23 19:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 16:46 [PATCH] huawei: fix AT^DDSETEX=2 timing devel
2012-03-10 16:46 ` devel
2012-03-23 19:13 ` Marcel Holtmann [this message]
2012-03-24 2:06 ` [PATCH v2] " devel
2012-03-24 2:06 ` devel
2012-03-24 4:14 ` Marcel Holtmann
2012-03-24 14:03 ` [PATCH v3] " devel
2012-03-24 14:03 ` devel
2012-03-24 18:51 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2012-03-10 2:26 Huawei voice output port issue + patch Marcel Holtmann
2012-03-10 12:22 ` [PATCH] huawei: fix AT^DDSETEX=2 timing Jarkko Lehtoranta
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=1332530001.1870.61.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=ofono@ofono.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