From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Jason Yan <yanaijie@huawei.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] scsi: remove extra white space at the end of the line
Date: Thu, 21 Dec 2017 05:41:00 +0000 [thread overview]
Message-ID: <c8a634e9-22b8-ac99-e0db-05b1566ed2e9@wdc.com> (raw)
In-Reply-To: <20171221024049.36509-1-yanaijie@huawei.com>
Jason,
On 12/21/17 11:40, Jason Yan wrote:
> My editor always try to remove the extra white space at the end of the
> line when I make some changes. I'm tired of adjusting them manually.
> Can we remove them in mainline?
>
> Signed-off-by: Jason Yan <yanaijie@huawei.com>
> ---
> drivers/scsi/scsi.c | 2 +-
> drivers/scsi/scsi_lib.c | 20 ++++++++++----------
> drivers/scsi/scsi_scan.c | 10 +++++-----
> drivers/scsi/scsi_sysfs.c | 4 ++--
> 4 files changed, 18 insertions(+), 18 deletions(-)
There are plenty in drivers/scsi/sd.c too :)
I would also love to get rid of these white spaces so that my emacs
stops looking like a Christmas tree all year long.
Last time I tried I got nacked...
Martin,
What about a (may be big) whitespace-only patch to clean up all the scsi
code and finally get checkpatch to stop screaming at us if we touch a
line near one with whitespaces (which can happen a lot...) ?
Best regards.
--
Damien Le Moal,
Western Digital
next prev parent reply other threads:[~2017-12-21 5:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 2:40 [PATCH] scsi: remove extra white space at the end of the line Jason Yan
2017-12-21 5:41 ` Damien Le Moal [this message]
2017-12-21 8:48 ` Johannes Thumshirn
2017-12-21 16:09 ` Bart Van Assche
2017-12-22 1:37 ` Jason Yan
2017-12-22 7:03 ` Johannes Thumshirn
2018-01-04 3:36 ` Martin K. Petersen
2018-01-08 8:21 ` Johannes Thumshirn
2017-12-24 1:10 ` Finn Thain
-- strict thread matches above, loose matches on Subject: below --
2018-01-22 23:41 Xose Vazquez Perez
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=c8a634e9-22b8-ac99-e0db-05b1566ed2e9@wdc.com \
--to=damien.lemoal@wdc.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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