lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 06 Oct 2020 11:35:35 -0700 From: Ranjani Sridharan <ranjani.sridharan@...ux.intel.com> To: Leon Romanovsky <leon@...nel.org>, Parav Pandit <parav@...dia.com> Cc: "alsa-devel@...a-project.org" <alsa-devel@...a-project.org>, "kuba@...nel.org" <kuba@...nel.org>, "parav@...lanox.com" <parav@...lanox.com>, "tiwai@...e.de" <tiwai@...e.de>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>, "fred.oh@...ux.intel.com" <fred.oh@...ux.intel.com>, "linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>, "dledford@...hat.com" <dledford@...hat.com>, "broonie@...nel.org" <broonie@...nel.org>, Jason Gunthorpe <jgg@...dia.com>, "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>, Dave Ertman <david.m.ertman@...el.com>, "dan.j.williams@...el.com" <dan.j.williams@...el.com>, "shiraz.saleem@...el.com" <shiraz.saleem@...el.com>, "davem@...emloft.net" <davem@...emloft.net>, "kiran.patil@...el.com" <kiran.patil@...el.com> Subject: Re: [PATCH v2 1/6] Add ancillary bus support On Tue, 2020-10-06 at 20:26 +0300, Leon Romanovsky wrote: > On Tue, Oct 06, 2020 at 05:09:09PM +0000, Parav Pandit wrote: > > > From: Leon Romanovsky <leon@...nel.org> > > > Sent: Tuesday, October 6, 2020 10:33 PM > > > > > > On Tue, Oct 06, 2020 at 10:18:07AM -0500, Pierre-Louis Bossart > > > wrote: > > > > Thanks for the review Leon. > > > > > > > > > > Add support for the Ancillary Bus, ancillary_device and > > > > > > ancillary_driver. > > > > > > It enables drivers to create an ancillary_device and bind > > > > > > an > > > > > > ancillary_driver to it. > > > > > > > > > > I was under impression that this name is going to be changed. > > > > > > > > It's part of the opens stated in the cover letter. > > > > > > ok, so what are the variants? > > > system bus (sysbus), sbsystem bus (subbus), crossbus ? > > Since the intended use of this bus is to > > (a) create sub devices that represent 'functional separation' and > > (b) second use case for subfunctions from a pci device, > > > > I proposed below names in v1 of this patchset. > > > > (a) subdev_bus > > It sounds good, just can we avoid "_" in the name and call it subdev? > > > (b) subfunction_bus While we're still discussing names, may I also suggest simply "software bus" instead? Thanks,Ranjani
Powered by blists - more mailing lists