From: "Ewan D. Milne" <emilne@redhat.com>
To: Colin King <colin.king@canonical.com>, linux-scsi@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] scsi: pm8001: remove space in a debug message
Date: Tue, 24 Nov 2020 18:23:12 -0500 [thread overview]
Message-ID: <b09bdc573715f51117c788a9b02d6b87c9735c4b.camel@redhat.com> (raw)
In-Reply-To: <20201124093828.307709-1-colin.king@canonical.com>
On Tue, 2020-11-24 at 09:38 +0000, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> There are two words that need separating with a space in a
> pm8001_dbg message. Fix it.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/scsi/pm8001/pm8001_hwi.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/scsi/pm8001/pm8001_hwi.c
> b/drivers/scsi/pm8001/pm8001_hwi.c
> index 08d6cc9b50db..c8d4d87c5473 100644
> --- a/drivers/scsi/pm8001/pm8001_hwi.c
> +++ b/drivers/scsi/pm8001/pm8001_hwi.c
> @@ -1031,7 +1031,7 @@ pm8001_chip_soft_rst(struct pm8001_hba_info
> *pm8001_ha)
> regVal = pm8001_cr32(pm8001_ha, 2,
> GSM_WRITE_DATA_PARITY_CHECK);
> pm8001_cw32(pm8001_ha, 2, GSM_WRITE_DATA_PARITY_CHECK,
> regVal3);
> pm8001_dbg(pm8001_ha, INIT,
> - "GSM 0x700048 - Write Data Parity Check Enableis set
> to = 0x%x\n",
> + "GSM 0x700048 - Write Data Parity Check Enable is
> set to = 0x%x\n",
> pm8001_cr32(pm8001_ha, 2,
> GSM_WRITE_DATA_PARITY_CHECK));
>
> /* step 13: bring the IOP and AAP1 out of reset */
Reviewed-by: Ewan D. Milne <emilne@redhat.com>
next prev parent reply other threads:[~2020-11-24 23:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 9:38 Colin King
2020-11-24 23:23 ` Ewan D. Milne [this message]
2020-11-26 14:01 ` Jinpu Wang
2020-12-01 4:35 ` Martin K. Petersen
2020-12-08 4:52 ` 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=b09bdc573715f51117c788a9b02d6b87c9735c4b.camel@redhat.com \
--to=emilne@redhat.com \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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
all inboxes | Powered by JetHome®