From: Stephen Hemminger <stephen@networkplumber.org>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev@dpdk.org, david.marchand@redhat.com, thomas@monjalon.net
Subject: Re: [PATCH 2/4] uapi: import VDUSE header from v6.14 kernel
Date: Tue, 20 May 2025 06:31:29 -0700 [thread overview]
Message-ID: <20250520063129.0c35a6ed@hermes.local> (raw)
In-Reply-To: <20250416123426.2638250-3-maxime.coquelin@redhat.com>
On Wed, 16 Apr 2025 14:34:24 +0200
Maxime Coquelin <maxime.coquelin@redhat.com> wrote:
> This header will be used by the Vhost library.
>
> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> ---
> kernel/linux/uapi/linux/vduse.h | 353 ++++++++++++++++++++++++++++++++
> kernel/linux/uapi/version | 2 +-
> 2 files changed, 354 insertions(+), 1 deletion(-)
> create mode 100644 kernel/linux/uapi/linux/vduse.h
This file should be generated by doing make headers_install in a Linux
kernel tree to ensure correct code.
If I do that with current 6.15 kernel tree it comes out different.
~/.../kernel/linux/uapi $ diff linux/vduse.h ~/kernel/linux/usr/include/linux/vduse.h
2,3c2,3
< #ifndef _UAPI_VDUSE_H_
< #define _UAPI_VDUSE_H_
---
> #ifndef _VDUSE_H_
> #define _VDUSE_H_
353c353
< #endif /* _UAPI_VDUSE_H_ */
---
> #endif /* _VDUSE_H_ */
next prev parent reply other threads:[~2025-05-20 13:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 12:34 [PATCH 0/4] Linux Kernel uAPI headers import Maxime Coquelin
2025-04-16 12:34 ` [PATCH 1/4] license: add exception for Linux Kernel uAPI headers Maxime Coquelin
2025-04-17 5:08 ` Hemant Agrawal
2025-04-16 12:34 ` [PATCH 2/4] uapi: import VDUSE header from v6.14 kernel Maxime Coquelin
2025-05-20 13:31 ` Stephen Hemminger [this message]
2025-04-16 12:34 ` [PATCH 3/4] vhost: use imported VDUSE uAPI header Maxime Coquelin
2025-04-16 12:34 ` [PATCH 4/4] ci: check licenses Maxime Coquelin
2025-04-16 18:59 ` Maxime Coquelin
2025-05-16 11:32 ` [PATCH 0/4] Linux Kernel uAPI headers import David Marchand
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=20250520063129.0c35a6ed@hermes.local \
--to=stephen@networkplumber.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=thomas@monjalon.net \
/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).