From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: john.garry@huawei.com, yanaijie@huawei.com,
Luo Jiaxing <luojiaxing@huawei.com>,
jejb@linux.ibm.com
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linuxarm@openeuler.org,
chenxiang66@hisilicon.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] scsi: libsas: few clean up patches
Date: Tue, 13 Apr 2021 01:48:14 -0400 [thread overview]
Message-ID: <161828336219.27813.14849607159789110806.b4-ty@oracle.com> (raw)
In-Reply-To: <1616675396-6108-1-git-send-email-luojiaxing@huawei.com>
On Thu, 25 Mar 2021 20:29:54 +0800, Luo Jiaxing wrote:
> Two types of errors are detected by the checkpatch.
> 1. Alignment between switches and cases
> 2. Improper use of some spaces
>
> Here are the clean up patches.
>
> Luo Jiaxing (2):
> scsi: libsas: make switch and case at the same indent in
> sas_to_ata_err()
> scsi: libsas: clean up for white spaces
>
> [...]
Applied to 5.13/scsi-queue, thanks!
[1/2] scsi: libsas: make switch and case at the same indent in sas_to_ata_err()
https://git.kernel.org/mkp/scsi/c/c03f2422b9f5
[2/2] scsi: libsas: clean up for white spaces
https://git.kernel.org/mkp/scsi/c/857a80bbd732
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2021-04-13 5:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 12:29 [PATCH v1 0/2] scsi: libsas: few clean up patches Luo Jiaxing
2021-03-25 12:29 ` [PATCH v1 1/2] scsi: libsas: make switch and case at the same indent in sas_to_ata_err() Luo Jiaxing
2021-03-25 12:29 ` [PATCH v1 2/2] scsi: libsas: clean up for white spaces Luo Jiaxing
2021-04-08 13:03 ` [PATCH v1 0/2] scsi: libsas: few clean up patches luojiaxing
2021-04-13 5:48 ` Martin K. Petersen [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=161828336219.27813.14849607159789110806.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=chenxiang66@hisilicon.com \
--cc=jejb@linux.ibm.com \
--cc=john.garry@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@openeuler.org \
--cc=luojiaxing@huawei.com \
--cc=yanaijie@huawei.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).