From: Ahmad Gani <reyuki@gnuweeb.org>
To: Alviro Iskandar Setiawan <alviro.iskandar@gnuweeb.org>
Cc: Ammar Faizi <ammarfaizi2@gnuweeb.org>,
"GNU/Weeb Mailing List" <gwml@vger.gnuweeb.org>
Subject: Re: [PATCH gwproxy v8 2/2] gwproxy: refactor code base to add experimental raw DNS backend
Date: Sat, 6 Sep 2025 13:17:24 +0700 [thread overview]
Message-ID: <CAADvAgo5OT0P-z3BEd8t20RvA_cRJ738LbCiTeUZ4YRt6xqBbg@mail.gmail.com> (raw)
In-Reply-To: <CAADvAgrjW-yAOoXU5RJpAsbLiZdHbjJHNJqeEM1gMxF3ZkseRA@mail.gmail.com>
On Sat, Sep 6, 2025 at 11:32 AM Ahmad Gani wrote:
> > On Fri, Aug 29, 2025 at 2:56 PM Ahmad Gani wrote:
> >> +void cp_nsaddr(struct gwp_dns_ctx *ctx, struct gwp_sockaddr *addr, uint8_t *addrlen)
> >> +{
> >> + *addr = ctx->ns_addr;
> >> + *addrlen = ctx->ns_addrlen;
> >> +}
> >
> > Why is this exposed globally? I don't think it's worth a function
> > call. Better be inlined.
>
> I can't access members of the gwp_dns_ctx struct directly from another
> file, as it seems to be treated as an opaque pointer outside of dns.c. If
> I make it an inline function, it would only be accessible within dns.c.
> Should I move the full declaration of the struct to the header file?
Oh, wait—I just realized you were talking about the inline keyword, not
static. My previous reply was unrelated; I misunderstood. In that case,
I'll add the inline keyword if it's not worth a function call.
--
Ahmad Gani
next prev parent reply other threads:[~2025-09-06 6:18 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 7:55 [PATCH gwproxy v8 0/2] Initial work on integration of DNS parser lib in gwproxy Ahmad Gani
2025-08-29 7:55 ` [PATCH gwproxy v8 1/2] dnsparser: Add dns parser code Ahmad Gani
2025-08-29 7:55 ` [PATCH gwproxy v8 2/2] gwproxy: refactor code base to add experimental raw DNS backend Ahmad Gani
2025-09-05 16:26 ` Alviro Iskandar Setiawan
2025-09-06 4:32 ` Ahmad Gani
2025-09-06 5:16 ` Ahmad Gani
2025-09-06 6:17 ` Ahmad Gani [this message]
2025-09-06 6:48 ` Ahmad Gani
2025-09-06 7:02 ` Alviro Iskandar Setiawan
2025-09-06 6:47 ` Alviro Iskandar Setiawan
2025-09-09 2:38 ` reyuki
2025-09-06 11:27 ` Ahmad Gani
2025-09-06 12:01 ` Alviro Iskandar Setiawan
2025-09-06 12:58 ` Ahmad Gani
2025-09-06 13:30 ` Alviro Iskandar Setiawan
2025-09-06 13:44 ` Alviro Iskandar Setiawan
2025-09-06 14:26 ` Ahmad Gani
2025-09-06 14:30 ` Alviro Iskandar Setiawan
2025-09-07 4:22 ` Ammar Faizi
2025-09-07 5:57 ` Ammar Faizi
2025-09-07 6:39 ` Ahmad Gani
2025-09-07 6:40 ` Ahmad Gani
2025-09-07 6:43 ` Ammar Faizi
2025-09-07 7:06 ` Ammar Faizi
2025-09-07 7:17 ` Ahmad Gani
2025-09-07 9:52 ` Ahmad Gani
2025-09-07 10:19 ` Ammar Faizi
2025-09-07 10:36 ` Ahmad Gani
2025-09-06 7:14 ` Alviro Iskandar Setiawan
2025-09-06 7:21 ` Ahmad Gani
2025-09-06 7:47 ` Alviro Iskandar Setiawan
2025-09-06 11:01 ` Ahmad Gani
2025-09-05 9:18 ` [PATCH gwproxy v8 0/2] Initial work on integration of DNS parser lib in gwproxy Ammar Faizi
2025-09-05 9:34 ` Alviro Iskandar Setiawan
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=CAADvAgo5OT0P-z3BEd8t20RvA_cRJ738LbCiTeUZ4YRt6xqBbg@mail.gmail.com \
--to=reyuki@gnuweeb.org \
--cc=alviro.iskandar@gnuweeb.org \
--cc=ammarfaizi2@gnuweeb.org \
--cc=gwml@vger.gnuweeb.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