From: Laurent Vivier <laurent@vivier.eu>
To: Aleksandar Markovic <aleksandar.markovic@rt-rk.com>,
qemu-devel@nongnu.org
Cc: lvivier@redhat.com, thuth@redhat.com, daniel.santos@pobox.com,
arikalo@wavecomp.com, jcmvbkbc@gmail.com, amarkovic@wavecomp.com,
nchen@wavecomp.com, philmd@redhat.com, aurelien@aurel32.net
Subject: Re: [Qemu-devel] [PATCH v4 3/5] linux-user: Add support the SIOC<G|S>IFPFLAGS ioctls for all targets
Date: Mon, 13 May 2019 13:46:12 +0200 [thread overview]
Message-ID: <8acf2e45-f2c4-36aa-7064-d23aa3f1bca2@vivier.eu> (raw)
In-Reply-To: <1556905846-14074-4-git-send-email-aleksandar.markovic@rt-rk.com>
On 03/05/2019 19:50, Aleksandar Markovic wrote:
> From: Neng Chen <nchen@wavecomp.com>
>
> Add support for getting and setting extended private flags of a
> network device via SIOCSIFPFLAGS and SIOCGIFPFLAGS ioctls.
>
> The ioctl numeric values are platform-independent and determined by
> the file include/uapi/linux/sockios.h in Linux kernel source code:
>
> #define SIOCSIFPFLAGS 0x8934
> #define SIOCGIFPFLAGS 0x8935
>
> These ioctls get (or set) the field ifr_flags of type short in the
> structure ifreq. Such functionality is achieved in QEMU by using
> MK_STRUCT() and MK_PTR() macros with an appropriate argument, as
> it was done for existing similar cases.
>
> Signed-off-by: Neng Chen <nchen@wavecomp.com>
> Signed-off-by: Aleksandar Markovic <amarkovic@wavecomp.com>
> Message-Id: <1554839486-3527-1-git-send-email-aleksandar.markovic@rt-rk.com>
> ---
> linux-user/ioctls.h | 2 ++
> linux-user/syscall_defs.h | 2 ++
> 2 files changed, 4 insertions(+)
Reviewed-by: Laurent Vivier <laurent@vivier.eu>
next prev parent reply other threads:[~2019-05-13 11:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 17:50 [Qemu-devel] [PATCH v4 0/5] linux-user: A set of miscellaneous patches Aleksandar Markovic
2019-05-03 17:50 ` Aleksandar Markovic
2019-05-03 17:50 ` [Qemu-devel] [PATCH v4 1/5] linux-user: Fix support for the SIOCATMARK and SIOCGPGRP ioctls for xtensa Aleksandar Markovic
2019-05-03 17:50 ` Aleksandar Markovic
2019-05-09 17:55 ` Laurent Vivier
2019-05-03 17:50 ` [Qemu-devel] [PATCH v4 2/5] linux-user: Add support for the SIOCSPGRP ioctl for all targets Aleksandar Markovic
2019-05-03 17:50 ` Aleksandar Markovic
2019-05-09 19:35 ` Laurent Vivier
2019-05-03 17:50 ` [Qemu-devel] [PATCH v4 3/5] linux-user: Add support the SIOC<G|S>IFPFLAGS ioctls " Aleksandar Markovic
2019-05-03 17:50 ` Aleksandar Markovic
2019-05-13 11:46 ` Laurent Vivier [this message]
2019-05-03 17:50 ` [Qemu-devel] [PATCH v4 4/5] linux-user: Add support for setsockopt() options IPV6_<ADD|DROP>_MEMBERSHIP Aleksandar Markovic
2019-05-03 17:50 ` Aleksandar Markovic
2019-05-13 12:00 ` Laurent Vivier
2019-05-03 17:50 ` [Qemu-devel] [PATCH v4 5/5] linux-user: Sanitize interp_info and, for mips only, init field fp_abi Aleksandar Markovic
2019-05-03 17:50 ` Aleksandar Markovic
2019-05-09 19:26 ` Laurent Vivier
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=8acf2e45-f2c4-36aa-7064-d23aa3f1bca2@vivier.eu \
--to=laurent@vivier.eu \
--cc=aleksandar.markovic@rt-rk.com \
--cc=amarkovic@wavecomp.com \
--cc=arikalo@wavecomp.com \
--cc=aurelien@aurel32.net \
--cc=daniel.santos@pobox.com \
--cc=jcmvbkbc@gmail.com \
--cc=lvivier@redhat.com \
--cc=nchen@wavecomp.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).