Searched hist:b5adbbf896d8375a1054ac56ac23194ac483ae96 (Results 1 – 6 of 6) sorted by relevance
/linux/drivers/s390/crypto/ |
H A D | zcrypt_cex2c.c | diff b5adbbf896d8375a1054ac56ac23194ac483ae96 Mon Jun 07 11:18:44 CEST 2021 Julian Wiedmann <jwi@linux.ibm.com> s390/ap: use the common driver-data pointer
The device struct provides a pointer for driver-private data. Use this in the zcrypt drivers (as vfio_ap already does), and then remove the custom pointer from the AP device structs.
As really_probe() will always clear the drvdata pointer on error, we no longer have to do so ourselves.
Signed-off-by: Julian Wiedmann <jwi@linux.ibm.com> Signed-off-by: Harald Freudenberger <freude@linux.ibm.com> Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
|
H A D | zcrypt_card.c | diff b5adbbf896d8375a1054ac56ac23194ac483ae96 Mon Jun 07 11:18:44 CEST 2021 Julian Wiedmann <jwi@linux.ibm.com> s390/ap: use the common driver-data pointer
The device struct provides a pointer for driver-private data. Use this in the zcrypt drivers (as vfio_ap already does), and then remove the custom pointer from the AP device structs.
As really_probe() will always clear the drvdata pointer on error, we no longer have to do so ourselves.
Signed-off-by: Julian Wiedmann <jwi@linux.ibm.com> Signed-off-by: Harald Freudenberger <freude@linux.ibm.com> Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
|
H A D | zcrypt_queue.c | diff b5adbbf896d8375a1054ac56ac23194ac483ae96 Mon Jun 07 11:18:44 CEST 2021 Julian Wiedmann <jwi@linux.ibm.com> s390/ap: use the common driver-data pointer
The device struct provides a pointer for driver-private data. Use this in the zcrypt drivers (as vfio_ap already does), and then remove the custom pointer from the AP device structs.
As really_probe() will always clear the drvdata pointer on error, we no longer have to do so ourselves.
Signed-off-by: Julian Wiedmann <jwi@linux.ibm.com> Signed-off-by: Harald Freudenberger <freude@linux.ibm.com> Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
|
H A D | zcrypt_cex4.c | diff b5adbbf896d8375a1054ac56ac23194ac483ae96 Mon Jun 07 11:18:44 CEST 2021 Julian Wiedmann <jwi@linux.ibm.com> s390/ap: use the common driver-data pointer
The device struct provides a pointer for driver-private data. Use this in the zcrypt drivers (as vfio_ap already does), and then remove the custom pointer from the AP device structs.
As really_probe() will always clear the drvdata pointer on error, we no longer have to do so ourselves.
Signed-off-by: Julian Wiedmann <jwi@linux.ibm.com> Signed-off-by: Harald Freudenberger <freude@linux.ibm.com> Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
|
H A D | zcrypt_cex2a.c | diff b5adbbf896d8375a1054ac56ac23194ac483ae96 Mon Jun 07 11:18:44 CEST 2021 Julian Wiedmann <jwi@linux.ibm.com> s390/ap: use the common driver-data pointer
The device struct provides a pointer for driver-private data. Use this in the zcrypt drivers (as vfio_ap already does), and then remove the custom pointer from the AP device structs.
As really_probe() will always clear the drvdata pointer on error, we no longer have to do so ourselves.
Signed-off-by: Julian Wiedmann <jwi@linux.ibm.com> Signed-off-by: Harald Freudenberger <freude@linux.ibm.com> Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
|
H A D | ap_bus.h | diff b5adbbf896d8375a1054ac56ac23194ac483ae96 Mon Jun 07 11:18:44 CEST 2021 Julian Wiedmann <jwi@linux.ibm.com> s390/ap: use the common driver-data pointer
The device struct provides a pointer for driver-private data. Use this in the zcrypt drivers (as vfio_ap already does), and then remove the custom pointer from the AP device structs.
As really_probe() will always clear the drvdata pointer on error, we no longer have to do so ourselves.
Signed-off-by: Julian Wiedmann <jwi@linux.ibm.com> Signed-off-by: Harald Freudenberger <freude@linux.ibm.com> Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
|