All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Parav Pandit <parav@nvidia.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH iproute2] uapi: add vdpa.h
Date: Mon, 18 Jul 2022 09:50:27 -0700	[thread overview]
Message-ID: <20220718095027.1ea6bbbc@hermes.local> (raw)
In-Reply-To: <PH0PR12MB5481AAD7096EA95956ED6801DC8C9@PH0PR12MB5481.namprd12.prod.outlook.com>

On Mon, 18 Jul 2022 16:40:30 +0000
Parav Pandit <parav@nvidia.com> wrote:

> + David
> 
> Hi Stephen,
> 
> > From: Stephen Hemminger <stephen@networkplumber.org>
> > Sent: Monday, July 18, 2022 12:31 PM
> > 
> > Iproute2 depends on kernel headers and all necessary kernel headers should
> > be in iproute tree. When vdpa was added the kernel header file was not.
> > 
> > Fixes: c2ecc82b9d4c ("vdpa: Add vdpa tool")
> > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>  
> 
> > ---
> >  include/uapi/linux/vdpa.h | 59
> > +++++++++++++++++++++++++++++++++++++++
> >  1 file changed, 59 insertions(+)
> >  create mode 100644 include/uapi/linux/vdpa.h
> > 
> > diff --git a/include/uapi/linux/vdpa.h b/include/uapi/linux/vdpa.h new file
> > mode 100644 index 000000000000..94e4dad1d86c
> > --- /dev/null
> > +++ b/include/uapi/linux/vdpa.h  
> 
> We kept this in vdpa/include/uapi/linux/vdpa.h after inputs from David.
> This is because vdpa was following rdma style sync with the kernel headers.
> Rdma subsystem kernel header is in rdma/include/uapi/rdma/rdma_netlink.h.
> 
> Any reason to take different route for vdpa?
> If so, duplicate file from vdpa/include/uapi/linux/vdpa.h should be removed.
> So that there is only one vdpa.h file.

Ok, sorry the semi-automated scan script didn't find the other one.

  reply	other threads:[~2022-07-18 16:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18 16:31 [PATCH iproute2] uapi: add vdpa.h Stephen Hemminger
2022-07-18 16:40 ` patchwork-bot+netdevbpf
2022-07-18 16:42   ` Parav Pandit
2022-07-18 16:40 ` Parav Pandit
2022-07-18 16:50   ` Stephen Hemminger [this message]
2022-07-18 16:55   ` Stephen Hemminger
2022-07-18 17:51     ` David Ahern
2022-07-18 20:18       ` Stephen Hemminger

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=20220718095027.1ea6bbbc@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=dsahern@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=parav@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.