diff options
| author | Parav Pandit <parav@nvidia.com> | 2022-06-13 22:52:23 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2022-07-21 21:24:33 +0200 |
| commit | 65d7a723fdda415eec901b7d7805e68f23359017 (patch) | |
| tree | 2b12a4e1ca405781884c41f43350721ac83dd1ff /drivers/bluetooth/bcm203x.c | |
| parent | b34dbeb2b0ece777a2256e820aaa809aff56abfd (diff) | |
vduse: Tie vduse mgmtdev and its device
[ Upstream commit 0e0348ac3f0a6e6606f1aa5acb1803ada913aa3d ]
vduse devices are not backed by any real devices such as PCI. Hence it
doesn't have any parent device linked to it.
Kernel driver model in [1] suggests to avoid an empty device
release callback.
Hence tie the mgmtdevice object's life cycle to an allocate dummy struct
device instead of static one.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/core-api/kobject.rst?h=v5.18-rc7#n284
Signed-off-by: Parav Pandit <parav@nvidia.com>
Message-Id: <20220613195223.473966-1-parav@nvidia.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Xie Yongji <xieyongji@bytedance.com>
Acked-by: Jason Wang <jasowang@redhat.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'drivers/bluetooth/bcm203x.c')
0 files changed, 0 insertions, 0 deletions