From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: dev@dpdk.org, david.marchand@redhat.com, thomas@monjalon.net
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: [PATCH 0/4] Linux Kernel uAPI headers import
Date: Wed, 16 Apr 2025 14:34:22 +0200 [thread overview]
Message-ID: <20250416123426.2638250-1-maxime.coquelin@redhat.com> (raw)
This series documents the license exception granted by both
the technical and governing boards to import uAPI header
files.
It also imports VDUSE uAPI header file from Kernel v6.14.
David Marchand (1):
ci: check licenses
Maxime Coquelin (3):
license: add exception for Linux Kernel uAPI headers
uapi: import VDUSE header from v6.14 kernel
vhost: use imported VDUSE uAPI header
.github/workflows/build.yml | 1 +
devtools/check-spdx-tag.sh | 2 +-
kernel/linux/uapi/linux/vduse.h | 353 ++++++++++++++++++++++++++++++++
kernel/linux/uapi/version | 2 +-
lib/vhost/meson.build | 5 +-
lib/vhost/vduse.c | 2 +-
lib/vhost/vduse.h | 22 --
license/Linux-syscall-note | 25 +++
license/exceptions.txt | 17 +-
9 files changed, 392 insertions(+), 37 deletions(-)
create mode 100644 kernel/linux/uapi/linux/vduse.h
create mode 100644 license/Linux-syscall-note
--
2.49.0
next reply other threads:[~2025-04-16 12:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 12:34 Maxime Coquelin [this message]
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-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
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=20250416123426.2638250-1-maxime.coquelin@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--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).