From: Thomas Huth <thuth@redhat.com>
To: linux-s390@vger.kernel.org, Tony Krowiak <akrowiak@linux.ibm.com>,
Halil Pasic <pasic@linux.ibm.com>,
Jason Herne <jjherne@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org,
Harald Freudenberger <freude@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>
Subject: [RFC PATCH] s390: vfio-ap: Register the vfio_ap module for the "ap" parent bus
Date: Wed, 1 Dec 2021 15:11:10 +0100 [thread overview]
Message-ID: <20211201141110.94636-1-thuth@redhat.com> (raw)
The crypto devices that we can use with the vfio_ap module are sitting
on the "ap" bus, not on the "vfio_ap" bus that the module defines
itself. With this change, the vfio_ap module now gets automatically
loaded if a supported crypto adapter is available in the host.
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
Note: Marked as "RFC" since I'm not 100% sure about it ...
please review carefully!
drivers/s390/crypto/vfio_ap_drv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/s390/crypto/vfio_ap_drv.c b/drivers/s390/crypto/vfio_ap_drv.c
index 4d2556bc7fe5..5580e40608a4 100644
--- a/drivers/s390/crypto/vfio_ap_drv.c
+++ b/drivers/s390/crypto/vfio_ap_drv.c
@@ -39,7 +39,7 @@ static struct ap_device_id ap_queue_ids[] = {
{ /* end of sibling */ },
};
-MODULE_DEVICE_TABLE(vfio_ap, ap_queue_ids);
+MODULE_DEVICE_TABLE(ap, ap_queue_ids);
/**
* vfio_ap_queue_dev_probe:
--
2.27.0
next reply other threads:[~2021-12-01 14:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 14:11 Thomas Huth [this message]
2021-12-01 17:10 ` [RFC PATCH] s390: vfio-ap: Register the vfio_ap module for the "ap" parent bus Harald Freudenberger
2021-12-02 7:13 ` Thomas Huth
2021-12-02 8:33 ` Harald Freudenberger
2021-12-03 19:26 ` Tony Krowiak
2021-12-08 13:46 ` Thomas Huth
2021-12-08 14:25 ` Cornelia Huck
2022-01-27 14:41 ` Tony Krowiak
2022-01-27 14:23 ` Tony Krowiak
2022-01-31 11:03 ` Harald Freudenberger
2021-12-13 15:44 ` Harald Freudenberger
2021-12-13 16:11 ` Cornelia Huck
2021-12-14 21:55 ` Tony Krowiak
2021-12-15 12:05 ` Thomas Huth
2021-12-15 12:51 ` Cornelia Huck
2021-12-15 14:38 ` Thomas Huth
2021-12-15 23:02 ` Halil Pasic
2021-12-16 10:39 ` Cornelia Huck
2021-12-16 11:25 ` Halil Pasic
2022-01-27 15:04 ` Tony Krowiak
2022-01-28 1:35 ` Halil Pasic
2022-01-27 14:48 ` Tony Krowiak
2022-01-27 14:46 ` Tony Krowiak
2021-12-14 21:28 ` Tony Krowiak
2022-01-27 10:33 ` Thomas Huth
2022-01-27 15:10 ` Tony Krowiak
2021-12-16 9:50 ` Harald Freudenberger
2021-12-16 10:44 ` Cornelia Huck
2022-01-27 14:45 ` Tony Krowiak
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=20211201141110.94636-1-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=akrowiak@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=jjherne@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).