From: David Marchand <david.marchand@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev@dpdk.org, techboard@dpdk.org, stephen@networkplumber.org,
ferruh.yigit@amd.com, thomas@monjalon.net,
mb@smartsharesystems.com
Subject: Re: [PATCH v3 0/3] Import Kernel uAPI header files
Date: Wed, 30 Oct 2024 09:44:38 +0100 [thread overview]
Message-ID: <CAJFAV8xVcm6Z_nvBfF4iMRu792HVSGCK1x5QbJ61FFt=SLat7w@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8ykGeqHwrmR0MtUaZj5y8JGfrY4JPEFZwa1OS497P=AEQ@mail.gmail.com>
On Tue, Oct 29, 2024 at 3:42 PM David Marchand
<david.marchand@redhat.com> wrote:
>
> On Mon, Oct 28, 2024 at 4:48 PM Maxime Coquelin
> <maxime.coquelin@redhat.com> wrote:
> >
> > This series enables importing Linux Kernel uAPI headers
> > into the DPDK repository. It aims at solving alignment
> > issues between the build system and the system applications
> > linked ot DPDK libraries are run on.
> >
> > It can also help simplify spaghetti code done to support
> > different versions of the Linux Kernel headers used by
> > the build system.
> >
> > Guidelines and import script are also part of first patch.
> > The uAPI checker script has been merged with the import
> > script in this V1, goals is to use it in CI for any patch
> > touching linux-headers/uapi.
> >
> > Follow-up patches are an example of imported uAPI inclusion
> > of VDUSE header into the Vhost library.
For the series,
Reviewed-by: David Marchand <david.marchand@redhat.com>
Series applied, thanks Maxime.
--
David Marchand
prev parent reply other threads:[~2024-10-30 8:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 15:48 Maxime Coquelin
2024-10-28 15:48 ` [PATCH v3 1/3] uapi: introduce kernel uAPI headers import Maxime Coquelin
2024-10-28 15:48 ` [PATCH v3 2/3] uapi: import VDUSE header Maxime Coquelin
2024-10-28 15:48 ` [PATCH v3 3/3] vduse: use imported VDUSE uAPI header Maxime Coquelin
2024-10-29 14:42 ` [PATCH v3 0/3] Import Kernel uAPI header files David Marchand
2024-10-30 8:44 ` David Marchand [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='CAJFAV8xVcm6Z_nvBfF4iMRu792HVSGCK1x5QbJ61FFt=SLat7w@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=maxime.coquelin@redhat.com \
--cc=mb@smartsharesystems.com \
--cc=stephen@networkplumber.org \
--cc=techboard@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).