From: Laurent Vivier <laurent@vivier.eu>
To: deller@kernel.org, "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
qemu-devel@nongnu.org, "Stefan Hajnoczi" <stefanha@gmail.com>
Cc: deller@gmx.de
Subject: Re: [PATCH v4 7/7] linux-user: netlink: Use QEMU_IFA_XXX values instead of IFA_XXX
Date: Wed, 22 Jan 2025 17:55:20 +0100 [thread overview]
Message-ID: <1e095753-6d29-4ac9-a74b-53a1f9b7c87c@vivier.eu> (raw)
In-Reply-To: <20250120213340.359195-8-deller@kernel.org>
Le 20/01/2025 à 22:33, deller@kernel.org a écrit :
> From: Helge Deller <deller@gmx.de>
>
> Convert existing places to use QEMU_IFA_XXX values.
>
> Signed-off-by: Helge Deller <deller@gmx.de>
> ---
> linux-user/fd-trans.c | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/linux-user/fd-trans.c b/linux-user/fd-trans.c
> index 105b1f0713..f83d1f79d5 100644
> --- a/linux-user/fd-trans.c
> +++ b/linux-user/fd-trans.c
> @@ -1192,21 +1192,21 @@ static abi_long host_to_target_data_addr_rtattr(struct rtattr *rtattr)
>
> switch (rtattr->rta_type) {
> /* binary: depends on family type */
> - case IFA_ADDRESS:
> - case IFA_LOCAL:
> + case QEMU_IFA_ADDRESS:
> + case QEMU_IFA_LOCAL:
> case QEMU_IFA_PROTO:
> break;
> /* string */
> - case IFA_LABEL:
> + case QEMU_IFA_LABEL:
> break;
> /* u32 */
> - case IFA_FLAGS:
> - case IFA_BROADCAST:
> + case QEMU_IFA_FLAGS:
> + case QEMU_IFA_BROADCAST:
> u32 = RTA_DATA(rtattr);
> *u32 = tswap32(*u32);
> break;
> /* struct ifa_cacheinfo */
> - case IFA_CACHEINFO:
> + case QEMU_IFA_CACHEINFO:
> ci = RTA_DATA(rtattr);
> ci->ifa_prefered = tswap32(ci->ifa_prefered);
> ci->ifa_valid = tswap32(ci->ifa_valid);
> @@ -1501,8 +1501,8 @@ static abi_long target_to_host_data_addr_rtattr(struct rtattr *rtattr)
> {
> switch (rtattr->rta_type) {
> /* binary: depends on family type */
> - case IFA_LOCAL:
> - case IFA_ADDRESS:
> + case QEMU_IFA_LOCAL:
> + case QEMU_IFA_ADDRESS:
> break;
> default:
> qemu_log_mask(LOG_UNIMP, "Unknown target IFA type: %d\n",
I would put this as patch one and adding the QEMU_IFA_XXX enum in this one.
Otherwise both patches (1 and 7) look good.
Thanks,
Laurent
prev parent reply other threads:[~2025-01-22 16:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 21:33 [PATCH v4 0/7] linux-user: Add support for various missing netlink sockopt entries deller
2025-01-20 21:33 ` [PATCH v4 1/7] linux-user: netlink: Add missing IFA_PROTO to host_to_target_data_addr_rtattr() deller
2025-01-22 16:53 ` Laurent Vivier
2025-01-22 21:20 ` Helge Deller
2025-01-24 7:46 ` Laurent Vivier
2025-01-20 21:33 ` [PATCH v4 2/7] linux-user: Use unique error messages for cmsg parsing deller
2025-01-20 21:33 ` [PATCH v4 3/7] linux-user: netlink: Add IP_PKTINFO " deller
2025-01-20 21:33 ` [PATCH v4 4/7] linux-user: netlink: Add emulation of IP_MULTICAST_IF deller
2025-01-20 21:33 ` [PATCH v4 5/7] linux-user: netlink: add netlink neighbour emulation deller
2025-01-20 21:33 ` [PATCH v4 6/7] linux-user: netlink: Add missing QEMU_IFLA entries deller
2025-01-20 21:33 ` [PATCH v4 7/7] linux-user: netlink: Use QEMU_IFA_XXX values instead of IFA_XXX deller
2025-01-22 16:55 ` Laurent Vivier [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=1e095753-6d29-4ac9-a74b-53a1f9b7c87c@vivier.eu \
--to=laurent@vivier.eu \
--cc=deller@gmx.de \
--cc=deller@kernel.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=stefanha@gmail.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 NNTP newsgroup(s).