From: Anthony Krowiak <akrowiak@linux.ibm.com>
To: Thorsten Blum <thorsten.blum@linux.dev>,
Halil Pasic <pasic@linux.ibm.com>,
Jason Herne <jjherne@linux.ibm.com>,
Harald Freudenberger <freude@linux.ibm.com>,
Holger Dengler <dengler@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390/vfio-ap: Fix indentation in vfio_ap_mdev_ioctl()
Date: Thu, 16 Jan 2025 10:41:33 -0500 [thread overview]
Message-ID: <6b898f8a-4ea0-421c-bbd2-cf318f0d5a5f@linux.ibm.com> (raw)
In-Reply-To: <20250116131146.105439-2-thorsten.blum@linux.dev>
On 1/16/25 8:11 AM, Thorsten Blum wrote:
> Remove any extra indentation to improve the code's readability.
Ironically, I noticed this the other day and was going to fix it.
Reviewed-by: Anthony Krowiak <akrowiak@linux.ibm.com>
>
> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
> ---
> drivers/s390/crypto/vfio_ap_ops.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/s390/crypto/vfio_ap_ops.c b/drivers/s390/crypto/vfio_ap_ops.c
> index a52c2690933f..155e19aef5df 100644
> --- a/drivers/s390/crypto/vfio_ap_ops.c
> +++ b/drivers/s390/crypto/vfio_ap_ops.c
> @@ -2199,8 +2199,8 @@ static ssize_t vfio_ap_mdev_ioctl(struct vfio_device *vdev,
> ret = vfio_ap_mdev_reset_queues(matrix_mdev);
> break;
> case VFIO_DEVICE_GET_IRQ_INFO:
> - ret = vfio_ap_get_irq_info(arg);
> - break;
> + ret = vfio_ap_get_irq_info(arg);
> + break;
> case VFIO_DEVICE_SET_IRQS:
> ret = vfio_ap_set_irqs(matrix_mdev, arg);
> break;
next prev parent reply other threads:[~2025-01-16 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 13:11 [PATCH] s390/vfio-ap: Fix indentation in vfio_ap_mdev_ioctl() Thorsten Blum
2025-01-16 15:41 ` Anthony Krowiak [this message]
2025-01-29 15:53 ` Alexander Gordeev
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=6b898f8a-4ea0-421c-bbd2-cf318f0d5a5f@linux.ibm.com \
--to=akrowiak@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=dengler@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 \
--cc=svens@linux.ibm.com \
--cc=thorsten.blum@linux.dev \
/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