From: patchwork-bot+ofono@kernel.org
To: Steve Schrock <steve.schrock@getcruise.com>
Cc: ofono@lists.linux.dev
Subject: Re: [PATCH v2 1/3] qmi: Discover timeout could cause a crash
Date: Mon, 18 Mar 2024 21:20:26 +0000 [thread overview]
Message-ID: <171079682683.31864.11297657489959559403.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240318183754.71578-1-steve.schrock@getcruise.com>
Hello:
This series was applied to ofono.git (master)
by Denis Kenzior <denkenz@gmail.com>:
On Mon, 18 Mar 2024 13:37:46 -0500 you wrote:
> Sometimes the QRTR discover timeout would occur simply because the
> control packets are being processed slowly. Handle this by extending
> the timeout each time a service is discovered. Then ensure the
> discover data on the queue exists before processing it, just in
> case there was an actual timeout.
> ---
> drivers/qmimodem/qmi.c | 50 ++++++++++++++++++++++++++----------------
> 1 file changed, 31 insertions(+), 19 deletions(-)
Here is the summary with links:
- [v2,1/3] qmi: Discover timeout could cause a crash
(no matching commit)
- [v2,2/3] qmi: Fix printing the wrong type for services
https://git.kernel.org/pub/scm/network/ofono/ofono.git/?id=85c935720dbd
- [v2,3/3] qmi: Allow QRTR services to be destroyed
https://git.kernel.org/pub/scm/network/ofono/ofono.git/?id=a703d1cc8e7e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-03-18 21:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 18:37 [PATCH v2 1/3] qmi: Discover timeout could cause a crash Steve Schrock
2024-03-18 18:37 ` [PATCH v2 2/3] qmi: Fix printing the wrong type for services Steve Schrock
2024-03-18 18:37 ` [PATCH v2 3/3] qmi: Allow QRTR services to be destroyed Steve Schrock
2024-03-18 21: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=171079682683.31864.11297657489959559403.git-patchwork-notify@kernel.org \
--to=patchwork-bot+ofono@kernel.org \
--cc=ofono@lists.linux.dev \
--cc=steve.schrock@getcruise.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 read-only IMAP folder(s) and NNTP newsgroup(s).