From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Colin King <colin.king@canonical.com>,
linux-scsi@vger.kernel.org, target-devel@vger.kernel.org
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] scsi: target: Fix spelling mistake "CONFLIFT" -> "CONFLICT"
Date: Wed, 22 Sep 2021 00:44:47 -0400 [thread overview]
Message-ID: <163228551953.26896.2559798529557281213.b4-ty@oracle.com> (raw)
In-Reply-To: <20210920183206.17477-1-colin.king@canonical.com>
On Mon, 20 Sep 2021 19:32:06 +0100, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There is a spelling mistake in a dev_err message. Fix it.
>
>
Applied to 5.15/scsi-fixes, thanks!
[1/1] scsi: target: Fix spelling mistake "CONFLIFT" -> "CONFLICT"
https://git.kernel.org/mkp/scsi/c/9a8ef2c73c72
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2021-09-22 4:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 18:32 [PATCH] scsi: target: Fix spelling mistake "CONFLIFT" -> "CONFLICT" Colin King
2021-09-22 4:44 ` Martin K. Petersen [this message]
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=163228551953.26896.2559798529557281213.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=target-devel@vger.kernel.org \
/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).