From: Finn Thain <fthain@telegraphics.com.au>
To: Hui Tang <tanghui20@huawei.com>
Cc: jejb@linux.ibm.com, martin.petersen@oracle.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 11/24] scsi: sun3_scsi: remove leading spaces before tabs
Date: Sun, 23 May 2021 08:37:15 +1000 (AEST) [thread overview]
Message-ID: <4bd6db59-414-221f-a8bc-49645511d56b@nippy.intranet> (raw)
In-Reply-To: <1621672648-39955-12-git-send-email-tanghui20@huawei.com>
On Sat, 22 May 2021, Hui Tang wrote:
> There are a few leading spaces before tabs and remove it by running
> the following commard:
>
> $ find . -name '*.[ch]' | xargs sed -r -i 's/^[ ]+\t/\t/'
>
Acked-by: Finn Thain <fthain@telegraphics.com.au>
Is there a reason why your regexp is anchored? I thought spaces before any
tab would be undesirable.
> Cc: Finn Thain <fthain@telegraphics.com.au>
> Signed-off-by: Hui Tang <tanghui20@huawei.com>
> ---
> drivers/scsi/sun3_scsi.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/scsi/sun3_scsi.c b/drivers/scsi/sun3_scsi.c
> index 2e3fbc2..6125ed3 100644
> --- a/drivers/scsi/sun3_scsi.c
> +++ b/drivers/scsi/sun3_scsi.c
> @@ -304,7 +304,7 @@ static int sun3scsi_dma_setup(struct NCR5380_hostdata *hostdata,
> sun3_udc_write(UDC_INT_ENABLE, UDC_CSR);
> #endif
>
> - return count;
> + return count;
>
> }
>
>
next prev parent reply other threads:[~2021-05-22 22:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 8:37 [PATCH 00/24] scsi: " Hui Tang
2021-05-22 8:37 ` [PATCH 01/24] scsi: aacraid: " Hui Tang
2021-05-22 8:37 ` [PATCH 02/24] scsi: aic7xxx: " Hui Tang
2021-05-22 8:37 ` [PATCH 03/24] scsi: arm: " Hui Tang
2021-05-22 8:37 ` [PATCH 04/24] scsi: sym53c8xx: " Hui Tang
2021-05-22 8:37 ` [PATCH 05/24] scsi: qla2xxx: " Hui Tang
2021-05-22 8:37 ` [PATCH 06/24] scsi: arcmsr: " Hui Tang
2021-05-22 8:37 ` [PATCH 07/24] scsi: ibmvfc: " Hui Tang
2021-05-22 8:37 ` [PATCH 08/24] scsi: megaraid: " Hui Tang
2021-05-22 8:37 ` [PATCH 09/24] scsi: zalon: " Hui Tang
2021-05-22 8:37 ` [PATCH 10/24] scsi: wd33c93: " Hui Tang
2021-05-22 8:37 ` [PATCH 11/24] scsi: sun3_scsi: " Hui Tang
2021-05-22 22:37 ` Finn Thain [this message]
2021-05-22 8:37 ` [PATCH 12/24] scsi: scsi_transport_spi: " Hui Tang
2021-05-22 8:37 ` [PATCH 13/24] scsi: scsi_transport_fc: " Hui Tang
2021-05-22 8:37 ` [PATCH 14/24] scsi: proc: " Hui Tang
2021-05-22 8:37 ` [PATCH 15/24] scsi: qlogicfas408: " Hui Tang
2021-05-22 8:37 ` [PATCH 16/24] scsi: qla1280: remove leading space " Hui Tang
2021-05-22 8:37 ` [PATCH 17/24] scsi: pcmcia: remove leading spaces " Hui Tang
2021-05-22 8:37 ` [PATCH 18/24] scsi: ncr53c8xx: " Hui Tang
2021-05-22 8:37 ` [PATCH 19/24] scsi: mesh: " Hui Tang
2021-05-22 8:37 ` [PATCH 20/24] scsi: mac53c94: " Hui Tang
2021-05-22 8:37 ` [PATCH 21/24] scsi: ips: " Hui Tang
2021-05-22 8:37 ` [PATCH 22/24] scsi: dpt_i2o: " Hui Tang
2021-05-22 8:37 ` [PATCH 23/24] scsi: dc395x: " Hui Tang
2021-05-22 8:37 ` [PATCH 24/24] scsi: aha1740: " Hui Tang
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=4bd6db59-414-221f-a8bc-49645511d56b@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=tanghui20@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
all inboxes | Powered by JetHome®