From: Denis Kenzior <denkenz@gmail.com>
To: connman@lists.linux.dev
Cc: Denis Kenzior <denkenz@gmail.com>
Subject: [PATCH 0/1] RFC: dnsproxy changes
Date: Wed, 22 Nov 2023 10:47:35 -0600 [thread overview]
Message-ID: <20231122165010.1217488-1-denkenz@gmail.com> (raw)
We had some changes to the DNS Proxy code lying around in an old branch.
I do not know anything about these, but maybe this is useful to someone,
especially since the dnsproxy code seems to be full of compile warnings.
These apply cleanly on top of the 1.31 tag.
Denis Kenzior (1):
dnsproxy: Changes
src/dnsproxy.c | 251 ++++++++++++++++++++++++++++++++++++++++++++-----
1 file changed, 228 insertions(+), 23 deletions(-)
--
2.42.0
next reply other threads:[~2023-11-22 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 16:47 Denis Kenzior [this message]
2023-11-22 16:47 ` [PATCH 1/1] dnsproxy: Changes Denis Kenzior
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=20231122165010.1217488-1-denkenz@gmail.com \
--to=denkenz@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).