From: Jason Gunthorpe <jgg@nvidia.com>
To: Eric Farman <farman@linux.ibm.com>
Cc: Matthew Rosato <mjrosato@linux.ibm.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Kirti Wankhede <kwankhede@nvidia.com>,
Vineeth Vijayan <vneethv@linux.ibm.com>,
Diana Craciun <diana.craciun@oss.nxp.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
David Airlie <airlied@gmail.com>,
linux-s390@vger.kernel.org, Yi Liu <yi.l.liu@intel.com>,
kvm@vger.kernel.org, Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
intel-gfx@lists.freedesktop.org,
Jason Herne <jjherne@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Eric Auger <eric.auger@redhat.com>,
Harald Freudenberger <freude@linux.ibm.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
intel-gvt-dev@lists.freedesktop.org,
Tony Krowiak <akrowiak@linux.ibm.com>,
Yishai Hadas <yishaih@nvidia.com>,
Cornelia Huck <cohuck@redhat.com>,
Peter Oberparleiter <oberpar@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Daniel Vetter <daniel@ffwll.ch>,
Abhishek Sahu <abhsahu@nvidia.com>
Subject: Re: [Intel-gfx] [PATCH v1 6/7] vfio/ccw: replace vfio_init_device with _alloc_
Date: Wed, 19 Oct 2022 14:15:30 -0300 [thread overview]
Message-ID: <Y1Awsh56Ur/cDrHh@nvidia.com> (raw)
In-Reply-To: <20221019162135.798901-7-farman@linux.ibm.com>
On Wed, Oct 19, 2022 at 06:21:34PM +0200, Eric Farman wrote:
> /*
> * Initialize a vfio_device so it can be registered to vfio core.
> - *
> - * Only vfio-ccw driver should call this interface.
> */
> int vfio_init_device(struct vfio_device *device, struct device *dev,
> const struct vfio_device_ops *ops)
> @@ -422,7 +420,6 @@ int vfio_init_device(struct vfio_device *device, struct device *dev,
> ida_free(&vfio.device_ida, device->index);
> return ret;
> }
> -EXPORT_SYMBOL_GPL(vfio_init_device);
Should be made static as well
Jason
next prev parent reply other threads:[~2022-10-19 17:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 16:21 [Intel-gfx] [PATCH v1 0/7] vfio-ccw parent rework Eric Farman
2022-10-19 16:21 ` [Intel-gfx] [PATCH v1 1/7] vfio/ccw: create a parent struct Eric Farman
2022-10-27 20:32 ` Eric Farman
2022-10-28 16:51 ` Matthew Rosato
2022-10-28 17:21 ` Eric Farman
2022-10-19 16:21 ` [Intel-gfx] [PATCH v1 2/7] vfio/ccw: remove private->sch Eric Farman
2022-10-28 18:43 ` Matthew Rosato
2022-10-19 16:21 ` [Intel-gfx] [PATCH v1 3/7] vfio/ccw: move private initialization to callback Eric Farman
2022-10-28 18:52 ` Matthew Rosato
2022-10-28 19:18 ` Eric Farman
2022-10-19 16:21 ` [Intel-gfx] [PATCH v1 4/7] vfio/ccw: move private to mdev lifecycle Eric Farman
2022-11-01 9:08 ` Tian, Kevin
2022-11-01 14:05 ` Eric Farman
2022-10-19 16:21 ` [Intel-gfx] [PATCH v1 5/7] vfio/ccw: remove release completion Eric Farman
2022-11-01 9:09 ` Tian, Kevin
2022-10-19 16:21 ` [Intel-gfx] [PATCH v1 6/7] vfio/ccw: replace vfio_init_device with _alloc_ Eric Farman
2022-10-19 17:15 ` Jason Gunthorpe [this message]
2022-10-19 17:57 ` Eric Farman
2022-10-20 12:26 ` Jason Gunthorpe
2022-11-01 9:10 ` Tian, Kevin
2022-10-19 16:21 ` [Intel-gfx] [PATCH v1 7/7] vfio: Remove vfio_free_device Eric Farman
2022-10-19 17:16 ` Jason Gunthorpe
2022-11-01 9:11 ` Tian, Kevin
2022-10-19 17:18 ` [Intel-gfx] [PATCH v1 0/7] vfio-ccw parent rework Jason Gunthorpe
2022-10-19 19:04 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2022-10-19 19:38 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
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=Y1Awsh56Ur/cDrHh@nvidia.com \
--to=jgg@nvidia.com \
--cc=abhsahu@nvidia.com \
--cc=agordeev@linux.ibm.com \
--cc=airlied@gmail.com \
--cc=akrowiak@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=daniel@ffwll.ch \
--cc=diana.craciun@oss.nxp.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric.auger@redhat.com \
--cc=farman@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jjherne@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=oberpar@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=rodrigo.vivi@intel.com \
--cc=svens@linux.ibm.com \
--cc=vneethv@linux.ibm.com \
--cc=yi.l.liu@intel.com \
--cc=yishaih@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox