($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: patchwork-bot+ofono@kernel.org
To: =?utf-8?q?Martin_Hundeb=C3=B8ll_=3Cmartin=40geanix=2Ecom=3E?=@ci.codeaurora.org
Cc: ofono@lists.linux.dev
Subject: Re: [PATCH] atmodem: fix detection of ATD*99 for non-muxed serial ports
Date: Thu, 25 Apr 2024 20:20:29 +0000	[thread overview]
Message-ID: <171407642905.12759.7904250069278840586.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240425115744.274891-1-martin@geanix.com>

Hello:

This patch was applied to ofono.git (master)
by Denis Kenzior <denkenz@gmail.com>:

On Thu, 25 Apr 2024 13:57:43 +0200 you wrote:
> The gprs context probe function has logic to detect whether CGDATA is
> supported by the modem, or if ATD*99 should be used instead. However, it
> seems like this logic was wrongly placed after registering for CGEV
> notification, which did an early return in case the passed chat did not
> have a slave.
> 
> Thus the ATD*99 detection was skipped for USB modems using separate
> "virtual" serial ports for command and data channels (i.e. ttyUSB0 for
> AT and ttyUSB1 for PPP).
> 
> [...]

Here is the summary with links:
  - atmodem: fix detection of ATD*99 for non-muxed serial ports
    https://git.kernel.org/pub/scm/network/ofono/ofono.git/?id=d42aad3e9553

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2024-04-25 20:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25 11:57 [PATCH] atmodem: fix detection of ATD*99 for non-muxed serial ports Martin Hundebøll
2024-04-25 20:20 ` patchwork-bot+ofono [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=171407642905.12759.7904250069278840586.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+ofono@kernel.org \
    --cc==?utf-8?q?Martin_Hundeb=C3=B8ll_=3Cmartin=40geanix=2Ecom=3E?=@ci.codeaurora.org \
    --cc=ofono@lists.linux.dev \
    /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).