From: Heiko Carstens <hca@linux.ibm.com>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: Stefan Haberland <sth@linux.ibm.com>,
Jan Hoeppner <hoeppner@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
linux-s390@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] s390/dasd: Fix spelling mistake "Ivalid" -> "Invalid"
Date: Tue, 27 Sep 2022 07:46:55 +0200 [thread overview]
Message-ID: <YzKOT6+oP4ckWBxh@osiris> (raw)
In-Reply-To: <20220923132103.2486724-1-colin.i.king@gmail.com>
On Fri, Sep 23, 2022 at 02:21:03PM +0100, Colin Ian King wrote:
> There is a spelling mistake in a pr_warn message. Fix it.
>
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>
> ---
> drivers/s390/block/dasd_ioctl.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/s390/block/dasd_ioctl.c b/drivers/s390/block/dasd_ioctl.c
> index d0ddf2cc9786..484de696839c 100644
> --- a/drivers/s390/block/dasd_ioctl.c
> +++ b/drivers/s390/block/dasd_ioctl.c
> @@ -401,7 +401,7 @@ dasd_ioctl_copy_pair_swap(struct block_device *bdev, void __user *argp)
> return -EFAULT;
> }
> if (memchr_inv(data.reserved, 0, sizeof(data.reserved))) {
> - pr_warn("%s: Ivalid swap data specified.\n",
> + pr_warn("%s: Invalid swap data specified.\n",
While at it you could also remove the full stop at the end of the
string, which is inconsistent to all other pr_warn() invocations
within the dasd device driver.
next prev parent reply other threads:[~2022-09-27 5:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 13:21 [PATCH][next] s390/dasd: Fix spelling mistake "Ivalid" -> "Invalid" Colin Ian King
2022-09-27 5:46 ` Heiko Carstens [this message]
2022-11-11 12:59 ` Stefan Haberland
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=YzKOT6+oP4ckWBxh@osiris \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=colin.i.king@gmail.com \
--cc=gor@linux.ibm.com \
--cc=hoeppner@linux.ibm.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=sth@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.