($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] qmimodem: Add USSD indication support
Date: Mon, 22 Feb 2021 10:06:31 -0600	[thread overview]
Message-ID: <9f0a4bab-1365-207a-436b-cd2fe569c93e@gmail.com> (raw)
In-Reply-To: <8fe191b9-0c3b-45ad-8701-d5311b64b3a6@ya.ru>

[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]

Hi Alexey,

On 2/19/21 9:30 AM, Alexey Andreyev wrote:
> Sorry for a noob html format, retrying from a custom client as plaintext:
> 
> Hello! My first patch, feel free to criticize :) This is to handle the USSD 
> Indication messages with the qmimodem driver.
> Higher-level KDE Plasma Mobile issue: 
> https://invent.kde.org/plasma-mobile/plasma-dialer/-/merge_requests/33
> Tested with Quectel EG25-G (Pinephone BH), looks like working, I'm able to 
> receive the expected QMI USSD Indication messages.
> 
> ---
>  From 2f041e6ba183a2f2a3309e139adef3d114bdc85b Mon Sep 17 00:00:00 2001
> From: Alexey Andreyev <aa13q@ya.ru>
> Date: Fri, 19 Feb 2021 15:47:42 +0300
> Subject: [PATCH] qmimodem: Add USSD indication support
> 
> Handle USSD QMI indication messages.
> Add support for UCS2 USS Data coding scheme.
> Check for User Action TLV type.
> ---
> drivers/qmimodem/ussd.c | 45 +++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 45 insertions(+)
> 

I had to hand-edit this patch for it to apply and then fix up the whitespace 
formatting.  Please get git send-email working properly for future submissions.

Applied, thanks.

Regards,
-Denis

      reply	other threads:[~2021-02-22 16:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19 15:21 [PATCH] qmimodem: Add USSD indication support Alexey Andreyev
2021-02-19 15:30 ` Alexey Andreyev
2021-02-22 16:06   ` Denis Kenzior [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=9f0a4bab-1365-207a-436b-cd2fe569c93e@gmail.com \
    --to=denkenz@gmail.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).