From: Johannes Thumshirn <jthumshirn@suse.de>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Bart Van Assche <Bart.VanAssche@wdc.com>,
"jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
"yanaijie@huawei.com" <yanaijie@huawei.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Damien Le Moal <Damien.LeMoal@wdc.com>
Subject: Re: [PATCH] scsi: remove extra white space at the end of the line
Date: Mon, 08 Jan 2018 09:21:47 +0100 [thread overview]
Message-ID: <mqdwp0skbfo.fsf@linux-x5ow.site> (raw)
In-Reply-To: <yq1608iz45y.fsf@oracle.com> (Martin K. Petersen's message of "Wed, 03 Jan 2018 22:36:09 -0500")
"Martin K. Petersen" <martin.petersen@oracle.com> writes:
> I am thoroughly annoyed by all the legacy whitespace problems. I've been
> working on two different sd patch series over the holidays and both
> caused me no end of grief due to legacy formatting issues.
>
> I have had an unbreak-sd patch sitting in my queue for several years but
> never pulled the trigger on it. For the usual reasons.
So we all share the same common pain points.
> I'm not particularly worried about bisection. But fixing whitespace does
> make it harder on the distro backporting front (Very pleased that you
> have now inadvertently volunteered to deal with all the issues that may
> arise at SUSE from such a subsystem-wide cleanup :).
>
> Anyway. I'm OK with fixing up the core pieces since they are the ones
> that annoy me the most. But I'm not sure we should enforce cleanups on
> drivers without an ack from the relevant maintainer. And for the
> unmaintained legacy baggage, I'm just not sure it's worth the hassle to
> clean things up. Fixing the crufty old things gives an illusion of the
> driver being actively worked on. I'd rather see dead code being left as
> such. Gives us a good indication of when it's safe to drop.
Well the drivers are more of a personal pain pain point but yes cleaning
up the core would be very much appreciated.
> One thing I specifically don't want is to open the flood gates for
> drive-by whitespace patches. I have no interest in wasting cycles on
> that. I generally only take arbitrary 3rd party cleanups if a driver is
> actively maintained and the maintainer specifically acks the change.
Agreed
> PS. I'll at least partially unbreak sd.c as part of the series I'll be
> posting shortly.
:-)
Byte,
Johannes
--
Johannes Thumshirn Storage
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2018-01-08 8:21 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
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 [this message]
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=mqdwp0skbfo.fsf@linux-x5ow.site \
--to=jthumshirn@suse.de \
--cc=Bart.VanAssche@wdc.com \
--cc=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