DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Subject: Re: [PATCH] uapi: update to 6.15 for vduse.h
Date: Tue, 10 Jun 2025 11:12:57 +0200	[thread overview]
Message-ID: <c0b51080-f51d-413a-9945-4cda470df4ea@redhat.com> (raw)
In-Reply-To: <20250609014106.11568-1-stephen@networkplumber.org>

Hi Stephen,

On 6/9/25 3:41 AM, Stephen Hemminger wrote:
> Use the header as produced by the kernel:
>   $ make headers_install

We use the header as produced by our import script (devtools/linux-
uapi.sh) as defined in the contribution guidelines and approved by the
tech and gov boards.

I'm fine with changing from _UAPI_VDUSE_H_ to _VDUSE_H_, but you need to
change it in the script not to break the checker.

> So that it exact match to what would be in distros and other tools.
> 
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
>   kernel/linux/uapi/linux/vduse.h | 6 +++---
>   1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/kernel/linux/uapi/linux/vduse.h b/kernel/linux/uapi/linux/vduse.h
> index 68a627d04a..f46269af34 100644
> --- a/kernel/linux/uapi/linux/vduse.h
> +++ b/kernel/linux/uapi/linux/vduse.h
> @@ -1,6 +1,6 @@
>   /* SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) */
> -#ifndef _UAPI_VDUSE_H_
> -#define _UAPI_VDUSE_H_
> +#ifndef _VDUSE_H_
> +#define _VDUSE_H_
>   
>   #include <linux/types.h>
>   
> @@ -350,4 +350,4 @@ struct vduse_dev_response {
>   	};
>   };
>   
> -#endif /* _UAPI_VDUSE_H_ */
> +#endif /* _VDUSE_H_ */


      reply	other threads:[~2025-06-10  9:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-09  1:41 Stephen Hemminger
2025-06-10  9:12 ` Maxime Coquelin [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=c0b51080-f51d-413a-9945-4cda470df4ea@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.org \
    /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).