From: Jakub Kicinski <kuba@kernel.org>
To: jane400 <jane400@postmarketos.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht
Subject: Re: [PATCH] uapi/if_arp.h: guard struct definition to not redefine libc's definitions
Date: Tue, 10 Sep 2024 17:27:01 -0700 [thread overview]
Message-ID: <20240910172701.74164f87@kernel.org> (raw)
In-Reply-To: <20240909092921.7377-2-jane400@postmarketos.org>
On Mon, 9 Sep 2024 11:28:55 +0200 jane400 wrote:
Could you please update the From fields in the email / the author of
the patch to have your full name like the sign off? Right now it says:
From: jane400 <jane400@postmarketos.org>
> musl libc defines the structs arpreq, arpreq_old and arphdr in
Could you add some reference to when the structs were added to musl?
Web link, or a version number, perhaps?
> diff --git a/include/uapi/linux/libc-compat.h b/include/uapi/linux/libc-compat.h
> index 8254c937c9f4..e722c213f18b 100644
> --- a/include/uapi/linux/libc-compat.h
> +++ b/include/uapi/linux/libc-compat.h
> @@ -194,6 +194,14 @@
> #define __UAPI_DEF_IF_NET_DEVICE_FLAGS_LOWER_UP_DORMANT_ECHO 1
> #endif
>
> +/* Definitions for if_arp.h */
> +#ifndef __UAPI_DEF_IF_ARP_ARPREQ
> +#define __UAPI_DEF_IF_ARP_ARPREQ 1
> +#endif
> +#ifndef __UAPI_DEF_IF_ARP_ARPHDR
> +#define __UAPI_DEF_IF_ARP_ARPHDR 1
> +#endif
> +
> /* Definitions for in.h */
> #ifndef __UAPI_DEF_IN_ADDR
> #define __UAPI_DEF_IN_ADDR 1
>
> base-commit: 89f5e14d05b4852db5ecdf222dc6a13edc633658
The code change looks almost good, I think you're missing the code for
handling getting included after the user space, tho? look around how
existing definitions are handled..
--
pw-bot: cr
prev parent reply other threads:[~2024-09-11 0:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 9:28 [PATCH] uapi/if_arp.h: guard struct definition to not redefine libc's definitions jane400
2024-09-11 0:27 ` Jakub Kicinski [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=20240910172701.74164f87@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jane400@postmarketos.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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 NNTP newsgroup(s).