linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: luojiaxing <luojiaxing@huawei.com>
To: <jinpu.wang@cloud.ionos.com>, <jejb@linux.ibm.com>,
	<martin.petersen@oracle.com>
Cc: <linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linuxarm@huawei.com>
Subject: Re: [PATCH v2 0/2] scsi: pm8001: tiny clean up patches
Date: Thu, 8 Apr 2021 20:25:58 +0800	[thread overview]
Message-ID: <ec7ff830-6d65-a174-52f2-db6573be5121@huawei.com> (raw)
In-Reply-To: <1617790059-43125-1-git-send-email-luojiaxing@huawei.com>

A reply to v1 cause v2 code need to be modified, so please ignore this, 
and directly check v3 later.


Thanks

Jiaxing

On 2021/4/7 18:07, Luo Jiaxing wrote:
> Several error is reported by checkpatch.pl, here are two patches to clean
> them up.
>
> ---
>     v1->v2:
>            1. modify AAP1_MEMMAP() to inline function
>            2. set flash_command_table and flash_error_table as const
> ---
>
> Luo Jiaxing (2):
>    scsi: pm8001: clean up for white space
>    scsi: pm8001: clean up for open brace
>
>   drivers/scsi/pm8001/pm8001_ctl.c | 26 +++++++++++---------------
>   drivers/scsi/pm8001/pm8001_ctl.h |  5 +++++
>   drivers/scsi/pm8001/pm8001_hwi.c | 14 +++++++-------
>   drivers/scsi/pm8001/pm8001_sas.c | 20 ++++++++++----------
>   drivers/scsi/pm8001/pm8001_sas.h |  2 +-
>   drivers/scsi/pm8001/pm80xx_hwi.c | 14 +++++++-------
>   6 files changed, 41 insertions(+), 40 deletions(-)
>


      parent reply	other threads:[~2021-04-08 12:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-07 10:07 [PATCH v2 0/2] scsi: pm8001: tiny clean up patches Luo Jiaxing
2021-04-07 10:07 ` [PATCH v2 1/2] scsi: pm8001: clean up for white space Luo Jiaxing
2021-04-07 10:07 ` [PATCH v2 2/2] scsi: pm8001: clean up for open brace Luo Jiaxing
2021-04-08 12:25 ` luojiaxing [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=ec7ff830-6d65-a174-52f2-db6573be5121@huawei.com \
    --to=luojiaxing@huawei.com \
    --cc=jejb@linux.ibm.com \
    --cc=jinpu.wang@cloud.ionos.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --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).