From: Joe Perches <joe@perches.com>
To: lijian_8010a29@163.com, james.smart@broadcom.com,
dick.kennedy@broadcom.com, jejb@linux.ibm.com,
martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
lijian <lijian@yulong.com>
Subject: Re: [PATCH v2] scsi: lpfc: lpfc_init: deleted these repeated words
Date: Wed, 09 Jun 2021 23:20:09 -0700 [thread overview]
Message-ID: <f36df404d219ff11546c3244054db348538e21db.camel@perches.com> (raw)
In-Reply-To: <20210610060921.67172-1-lijian_8010a29@163.com>
On Thu, 2021-06-10 at 14:09 +0800, lijian_8010a29@163.com wrote:
> From: lijian <lijian@yulong.com>
>
> deleted these repeated words 'the', 'using' and 'be' in the comments.
>
> Signed-off-by: lijian <lijian@yulong.com>
> ---
> v2: Fix these typos
> Change 'irrelvant' to 'irrelevant'.
> Change 'will be re-try' to 'will be retried'.
This should be part of the commit message.
The content below the --- line is not added to any git commit.
> diff --git a/drivers/scsi/lpfc/lpfc_init.c b/drivers/scsi/lpfc/lpfc_init.c
[]
> @@ -5894,7 +5894,7 @@ lpfc_sli4_async_fip_evt(struct lpfc_hba *phba,
> phba->fcf.fcf_flag &= ~FCF_ACVL_DISC;
> spin_unlock_irq(&phba->hbalock);
> /*
> - * Last resort will be re-try on
> + * Last resort will be retried on
retried on the current/to retry (with?) the current
Your spelling fixes seem reasonable but perhaps you could find a
fully fluent English speaker/writer to review your proposals before
submitting English grammar patches.
prev parent reply other threads:[~2021-06-10 6:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 6:09 [PATCH v2] scsi: lpfc: lpfc_init: deleted these repeated words lijian_8010a29
2021-06-10 6:20 ` Joe Perches [this message]
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=f36df404d219ff11546c3244054db348538e21db.camel@perches.com \
--to=joe@perches.com \
--cc=dick.kennedy@broadcom.com \
--cc=james.smart@broadcom.com \
--cc=jejb@linux.ibm.com \
--cc=lijian@yulong.com \
--cc=lijian_8010a29@163.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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).