From: patchwork-bot+connman@kernel.org
To: Brian Fukano <bfukano@gmail.com>
Cc: connman@lists.linux.dev
Subject: Re: [PATCH v2] dnsproxy: Fix cached ttl update
Date: Mon, 22 Apr 2024 22:50:28 +0000 [thread overview]
Message-ID: <171382622806.8811.11491387747740242977.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240422193805.123689-1-bfukano@gmail.com>
Hello:
This patch was applied to connman.git (master)
by Denis Kenzior <denkenz@gmail.com>:
On Mon, 22 Apr 2024 12:38:05 -0700 you wrote:
> This bug was exposed after fixing the signedness comparison warnings
> found in dnsproxy.c update_cached_ttl() consistently comes up two
> bytes short when processing the last record.
> ---
> src/dnsproxy.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
Here is the summary with links:
- [v2] dnsproxy: Fix cached ttl update
https://git.kernel.org/pub/scm/network/connman/connman.git/?id=3ba031745fe0
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-04-22 22:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 19:38 [PATCH v2] dnsproxy: Fix cached ttl update Brian Fukano
2024-04-22 22:50 ` patchwork-bot+connman [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=171382622806.8811.11491387747740242977.git-patchwork-notify@kernel.org \
--to=patchwork-bot+connman@kernel.org \
--cc=bfukano@gmail.com \
--cc=connman@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