From: Randy Dunlap <rdunlap@infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
mdr@sgi.com, jejb@linux.ibm.com, martin.petersen@oracle.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: Mundane spelling fixes in the file qla1280.c
Date: Sun, 14 Mar 2021 19:25:06 -0700 [thread overview]
Message-ID: <410164a3-d00f-f2bf-3eb2-49a163add143@infradead.org> (raw)
In-Reply-To: <20210315021610.2089087-1-unixbhaskar@gmail.com>
On 3/14/21 7:16 PM, Bhaskar Chowdhury wrote:
>
> s/quantites/quantities/
> s/Unfortunely/Unfortunately/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> drivers/scsi/qla1280.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/scsi/qla1280.c b/drivers/scsi/qla1280.c
> index 46de2541af25..95008811b2d2 100644
> --- a/drivers/scsi/qla1280.c
> +++ b/drivers/scsi/qla1280.c
> @@ -633,13 +633,13 @@ static int qla1280_read_nvram(struct scsi_qla_host *ha)
> * to be read a word (two bytes) at a time.
> *
> * The net result of this would be that the word (and
> - * doubleword) quantites in the firmware would be correct, but
> + * doubleword) quantities in the firmware would be correct, but
> * the bytes would be pairwise reversed. Since most of the
> - * firmware quantites are, in fact, bytes, we do an extra
> + * firmware quantities are, in fact, bytes, we do an extra
> * le16_to_cpu() in the firmware read routine.
> *
> * The upshot of all this is that the bytes in the firmware
> - * are in the correct places, but the 16 and 32 bit quantites
> + * are in the correct places, but the 16 and 32 bit quantities
> * are still in little endian format. We fix that up below by
> * doing extra reverses on them */
> nv->isp_parameter = cpu_to_le16(nv->isp_parameter);
> @@ -687,7 +687,7 @@ qla1280_info(struct Scsi_Host *host)
> * The mid-level driver tries to ensures that queuecommand never gets invoked
> * concurrently with itself or the interrupt handler (although the
> * interrupt handler may call this routine as part of request-completion
> - * handling). Unfortunely, it sometimes calls the scheduler in interrupt
> + * handling). Unfortunately, it sometimes calls the scheduler in interrupt
> * context which is a big NO! NO!.
> **************************************************************************/
> static int
> --
--
~Randy
next prev parent reply other threads:[~2021-03-15 2:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 2:16 [PATCH] scsi: Mundane spelling fixes in the file qla1280.c Bhaskar Chowdhury
2021-03-15 2:25 ` Randy Dunlap [this message]
2021-03-19 3:46 ` 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=410164a3-d00f-f2bf-3eb2-49a163add143@infradead.org \
--to=rdunlap@infradead.org \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mdr@sgi.com \
--cc=unixbhaskar@gmail.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;
as well as URLs for NNTP newsgroup(s).