From: David Ahern <dsahern@gmail.com>
To: Parav Pandit <parav@nvidia.com>,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, stephen@networkplumber.org,
mst@redhat.com, jasowang@redhat.com
Subject: Re: [PATCH iproute2-next v3 1/5] Add kernel headers
Date: Wed, 3 Feb 2021 18:37:22 -0700 [thread overview]
Message-ID: <abc71731-012e-eaa4-0274-5347fc99c249@gmail.com> (raw)
In-Reply-To: <20210202103518.3858-2-parav@nvidia.com>
On 2/2/21 3:35 AM, Parav Pandit wrote:
> Add kernel headers to commit from kernel tree [1].
> 79991caf5202c7 ("vdpa_sim_net: Add support for user supported devices")
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git branch: linux-next
>
Thinking about this flow a bit more: If new features to
uapi/linux/vdpa.h are coming through Michael's tree which is not sent
via net-next, then I think this header needs to be managed like the rdma
uapi files. In that case it should be added to iproute2 as
vdpa/include/uapi/linux and you / vdpa dev's will be responsible for
managing updates. In general, this should not be a trend, but seems to
be needed since vdpa is more than just a networking tool.
next prev parent reply other threads:[~2021-02-04 1:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 11:26 [PATCH iproute2-next 0/2] Add vdpa device management tool Parav Pandit
2021-01-22 11:26 ` [PATCH iproute2-next 1/2] Add kernel headers Parav Pandit
2021-01-22 11:26 ` [PATCH iproute2-next 2/2] vdpa: Add vdpa tool Parav Pandit
2021-01-26 4:22 ` David Ahern
2021-01-26 13:26 ` Parav Pandit
2021-01-28 18:43 ` [PATCH iproute2-next v2 0/2] Add vdpa device management tool Parav Pandit
2021-01-28 18:43 ` [PATCH iproute2-next v2 1/2] Add kernel headers Parav Pandit
2021-01-28 18:43 ` [PATCH iproute2-next v2 2/2] vdpa: Add vdpa tool Parav Pandit
2021-01-29 3:23 ` Parav Pandit
2021-02-02 10:35 ` [PATCH iproute2-next v3 0/5] Add vdpa device management tool Parav Pandit
2021-02-02 10:35 ` [PATCH iproute2-next v3 1/5] Add kernel headers Parav Pandit
2021-02-04 1:37 ` David Ahern [this message]
2021-02-05 17:54 ` Parav Pandit
2021-02-02 10:35 ` [PATCH iproute2-next v3 2/5] utils: Add helper routines for indent handling Parav Pandit
2021-02-02 10:35 ` [PATCH iproute2-next v3 3/5] utils: Add generic socket helpers Parav Pandit
2021-02-02 10:35 ` [PATCH iproute2-next v3 4/5] utils: Add helper to map string to unsigned int Parav Pandit
2021-02-02 10:35 ` [PATCH iproute2-next v3 5/5] vdpa: Add vdpa tool Parav Pandit
2021-02-04 3:16 ` [PATCH iproute2-next v3 0/5] Add vdpa device management tool Jason Wang
2021-02-04 11:15 ` Adrian Moreno
2021-02-05 3:40 ` Jason Wang
2021-02-05 17:53 ` Parav Pandit
2021-02-05 18:06 ` Adrian Moreno
2021-02-05 18:07 ` Adrian Moreno
2021-02-05 18:10 ` [PATCH iproute2-next v4 " Parav Pandit
2021-02-05 18:10 ` [PATCH iproute2-next v4 1/5] Add kernel headers Parav Pandit
2021-02-08 15:47 ` David Ahern
2021-02-10 18:28 ` Parav Pandit
2021-02-05 18:10 ` [PATCH iproute2-next v4 2/5] utils: Add helper routines for indent handling Parav Pandit
2021-02-05 18:10 ` [PATCH iproute2-next v4 3/5] utils: Add generic socket helpers Parav Pandit
2021-02-05 18:10 ` [PATCH iproute2-next v4 4/5] utils: Add helper to map string to unsigned int Parav Pandit
2021-02-05 18:10 ` [PATCH iproute2-next v4 5/5] vdpa: Add vdpa tool Parav Pandit
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=abc71731-012e-eaa4-0274-5347fc99c249@gmail.com \
--to=dsahern@gmail.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=parav@nvidia.com \
--cc=stephen@networkplumber.org \
--cc=virtualization@lists.linux-foundation.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).