[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BY5PR12MB43221EDD86F33912C1A591E9DCB29@BY5PR12MB4322.namprd12.prod.outlook.com>
Date: Fri, 5 Feb 2021 17:54:28 +0000
From: Parav Pandit <parav@...dia.com>
To: David Ahern <dsahern@...il.com>,
"virtualization@...ts.linux-foundation.org"
<virtualization@...ts.linux-foundation.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"stephen@...workplumber.org" <stephen@...workplumber.org>,
"mst@...hat.com" <mst@...hat.com>,
"jasowang@...hat.com" <jasowang@...hat.com>
Subject: RE: [PATCH iproute2-next v3 1/5] Add kernel headers
> From: David Ahern <dsahern@...il.com>
> Sent: Thursday, February 4, 2021 7:07 AM
>
> 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.
Ok. Sending v4 to relocate it to the recommended directory.
Thanks.
Powered by blists - more mailing lists