From: James Smart <james.smart@broadcom.com>
To: Colin King <colin.king@canonical.com>,
Dick Kennedy <dick.kennedy@broadcom.com>,
"James E . J . Bottomley" <jejb@linux.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] scsi: lpfc: fix inconsistent indenting
Date: Tue, 07 Jul 2020 17:00:14 +0000 [thread overview]
Message-ID: <e4686e05-e06e-93d1-e332-f6403b7eab9b@broadcom.com> (raw)
In-Reply-To: <20200707150018.823350-1-colin.king@canonical.com>
On 7/7/2020 8:00 AM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Fix smatch warning:
> drivers/scsi/lpfc/lpfc_sli.c:15156 lpfc_cq_poll_hdler() warn: inconsistent
> indenting
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/scsi/lpfc/lpfc_sli.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/scsi/lpfc/lpfc_sli.c b/drivers/scsi/lpfc/lpfc_sli.c
> index e17675381cb8..92fc6527e7ee 100644
> --- a/drivers/scsi/lpfc/lpfc_sli.c
> +++ b/drivers/scsi/lpfc/lpfc_sli.c
> @@ -15153,7 +15153,7 @@ static int lpfc_cq_poll_hdler(struct irq_poll *iop, int budget)
> {
> struct lpfc_queue *cq = container_of(iop, struct lpfc_queue, iop);
>
> - __lpfc_sli4_hba_process_cq(cq, LPFC_IRQ_POLL);
> + __lpfc_sli4_hba_process_cq(cq, LPFC_IRQ_POLL);
>
> return 1;
> }
Reviewed-by: James Smart <james.smart@broadcom.com>
-- james
next prev parent reply other threads:[~2020-07-07 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 15:00 [PATCH][next] scsi: lpfc: fix inconsistent indenting Colin King
2020-07-07 17:00 ` James Smart [this message]
2020-07-08 6:06 ` 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=e4686e05-e06e-93d1-e332-f6403b7eab9b@broadcom.com \
--to=james.smart@broadcom.com \
--cc=colin.king@canonical.com \
--cc=dick.kennedy@broadcom.com \
--cc=jejb@linux.ibm.com \
--cc=kernel-janitors@vger.kernel.org \
--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).