From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Colin King <colin.king@canonical.com>
Cc: "Nicholas A . Bellinger" <nab@linux-iscsi.org>,
Bart Van Assche <bvanassche@acm.org>,
target-devel@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: iscsi: target: fix spelling mistake "entires" -> "entries"
Date: Mon, 17 Sep 2018 06:33:03 +0000 [thread overview]
Message-ID: <yq1y3c0skf4.fsf@oracle.com> (raw)
In-Reply-To: <20180914122808.5447-1-colin.king@canonical.com> (Colin King's message of "Fri, 14 Sep 2018 13:28:08 +0100")
Colin,
> Trivial fix to spelling mistake in function name and comment
Applied to 4.20/scsi-queue, thanks!
--
Martin K. Petersen Oracle Linux Engineering
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Colin King <colin.king@canonical.com>
Cc: "Nicholas A . Bellinger" <nab@linux-iscsi.org>,
Bart Van Assche <bvanassche@acm.org>,
target-devel@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: iscsi: target: fix spelling mistake "entires" -> "entries"
Date: Mon, 17 Sep 2018 02:33:03 -0400 [thread overview]
Message-ID: <yq1y3c0skf4.fsf@oracle.com> (raw)
In-Reply-To: <20180914122808.5447-1-colin.king@canonical.com> (Colin King's message of "Fri, 14 Sep 2018 13:28:08 +0100")
Colin,
> Trivial fix to spelling mistake in function name and comment
Applied to 4.20/scsi-queue, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2018-09-17 6:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 12:28 [PATCH] scsi: iscsi: target: fix spelling mistake "entires" -> "entries" Colin King
2018-09-14 12:28 ` Colin King
2018-09-17 6:33 ` Martin K. Petersen [this message]
2018-09-17 6:33 ` Martin K. Petersen
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=yq1y3c0skf4.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=bvanassche@acm.org \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nab@linux-iscsi.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 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.