From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: brking@us.ibm.com, jejb@linux.ibm.com,
martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: rdunlap@infradead.org, Bhaskar Chowdhury <unixbhaskar@gmail.com>
Subject: [PATCH] drivers: scsi: File ipr.c gets few spelling fixes
Date: Fri, 5 Feb 2021 14:42:57 +0530 [thread overview]
Message-ID: <20210205091257.484726-1-unixbhaskar@gmail.com> (raw)
s/Enablement/Entablement/
s/specfied/specified/
s/confgurations/configurations/
Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
---
drivers/scsi/ipr.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/scsi/ipr.c b/drivers/scsi/ipr.c
index e451102b9a29..c12c0a309c54 100644
--- a/drivers/scsi/ipr.c
+++ b/drivers/scsi/ipr.c
@@ -16,7 +16,7 @@
*
* IBM pSeries: PCI-X Dual Channel Ultra 320 SCSI RAID Adapter
* PCI-X Dual Channel Ultra 320 SCSI Adapter
- * PCI-X Dual Channel Ultra 320 SCSI RAID Enablement Card
+ * PCI-X Dual Channel Ultra 320 SCSI RAID Entablement Card
* Embedded SCSI adapter on p615 and p655 systems
*
* Supported Hardware Features:
@@ -2470,7 +2470,7 @@ static void ipr_log_sis64_device_error(struct ipr_ioa_cfg *ioa_cfg,
}
/**
- * ipr_get_error - Find the specfied IOASC in the ipr_error_table.
+ * ipr_get_error - Find the specified IOASC in the ipr_error_table.
* @ioasc: IOASC
*
* This function will return the index of into the ipr_error_table
@@ -7202,7 +7202,7 @@ static const u16 ipr_blocked_processors[] = {
*
* Adapters that use Gemstone revision < 3.1 do not work reliably on
* certain pSeries hardware. This function determines if the given
- * adapter is in one of these confgurations or not.
+ * adapter is in one of these configurations or not.
*
* Return value:
* 1 if adapter is not supported / 0 if adapter is supported
--
2.30.0
next reply other threads:[~2021-02-05 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 9:12 Bhaskar Chowdhury [this message]
2021-02-05 17:10 ` Randy Dunlap
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=20210205091257.484726-1-unixbhaskar@gmail.com \
--to=unixbhaskar@gmail.com \
--cc=brking@us.ibm.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=rdunlap@infradead.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®