From: Randy Dunlap <rdunlap@infradead.org>
To: Yu Zhe <yuzhe@nfschina.com>,
kashyap.desai@broadcom.com, sumit.saxena@broadcom.com,
shivasharan.srikanteshwara@broadcom.com, jejb@linux.ibm.com,
martin.petersen@oracle.com
Cc: megaraidlinux.pdl@broadcom.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
liqiong@nfschina.com
Subject: Re: [PATCH] scsi: megaraid_sas: fix some spelling mistakes in comment
Date: Thu, 24 Nov 2022 08:21:35 -0800 [thread overview]
Message-ID: <387ebede-048b-203c-ffe7-7f0ff2014d3c@infradead.org> (raw)
In-Reply-To: <20221124092514.32032-1-yuzhe@nfschina.com>
Hi--
These changes all look good.
One small nit below:
On 11/24/22 01:25, Yu Zhe wrote:
> Fix typos in comment.
>
> Signed-off-by: Yu Zhe <yuzhe@nfschina.com>
> ---
> drivers/scsi/megaraid/megaraid_sas_fusion.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/scsi/megaraid/megaraid_sas_fusion.c b/drivers/scsi/megaraid/megaraid_sas_fusion.c
> index 6650f8c8e9b0..c53c29a0a018 100644
> --- a/drivers/scsi/megaraid/megaraid_sas_fusion.c
> +++ b/drivers/scsi/megaraid/megaraid_sas_fusion.c
> @@ -80,7 +80,7 @@ static void megasas_fusion_crash_dump(struct megasas_instance *instance);
> * @ocr_context: If called from OCR context this will
> * be set to 1, else 0
> *
> - * This function initates a chip reset followed by a wait for controller to
> + * This function initiates a chip reset followed by a wait for controller to
> * transition to ready state.
> * During this, driver will block all access to PCI config space from userspace
> */
> @@ -334,7 +334,7 @@ megasas_fire_cmd_fusion(struct megasas_instance *instance,
> *
> * This function is only for fusion controllers.
> * Update host can queue, if firmware downgrade max supported firmware commands.
> - * Firmware upgrade case will be skiped because underlying firmware has
> + * Firmware upgrade case will be skipped because underlying firmware has
> * more resource than exposed to the OS.
> *
> */
> @@ -2588,7 +2588,7 @@ static void megasas_stream_detect(struct megasas_instance *instance,
> if ((io_info->ldStartBlock != current_sd->next_seq_lba) &&
> ((!io_info->isRead) || (!is_read_ahead)))
> /*
> - * Once the API availible we need to change this.
> + * Once the API available we need to change this.
* Once the API is available we need to change this.
> * At this point we are not allowing any gap
> */
> continue;
> @@ -4650,7 +4650,7 @@ megasas_issue_tm(struct megasas_instance *instance, u16 device_handle,
> }
>
> /*
> - * megasas_fusion_smid_lookup : Look for fusion command correpspodning to SCSI
> + * megasas_fusion_smid_lookup : Look for fusion command corresponding to SCSI
> * @instance: per adapter struct
> *
> * Return Non Zero index, if SMID found in outstanding commands
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
--
~Randy
next prev parent reply other threads:[~2022-11-24 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 9:25 Yu Zhe
2022-11-24 16:21 ` Randy Dunlap [this message]
2022-11-25 2:07 ` [PATCH v2] " Yu Zhe
2022-11-26 2:59 ` Martin K. Petersen
2022-12-01 3:45 ` 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=387ebede-048b-203c-ffe7-7f0ff2014d3c@infradead.org \
--to=rdunlap@infradead.org \
--cc=jejb@linux.ibm.com \
--cc=kashyap.desai@broadcom.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=liqiong@nfschina.com \
--cc=martin.petersen@oracle.com \
--cc=megaraidlinux.pdl@broadcom.com \
--cc=shivasharan.srikanteshwara@broadcom.com \
--cc=sumit.saxena@broadcom.com \
--cc=yuzhe@nfschina.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 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®