From: Leon Romanovsky <leon@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH master] module: remove never implemented MODULE_SUPPORTED_DEVICE
Date: Sat, 20 Mar 2021 11:23:05 +0200 [thread overview]
Message-ID: <YFW++S+TTCK/3dfO@unreal> (raw)
In-Reply-To: <CAHk-=wjZoOr4yqAAxricTsachacAUvcKt6HOfxyReCyMN0V=QQ@mail.gmail.com>
On Thu, Mar 18, 2021 at 10:55:51AM -0700, Linus Torvalds wrote:
> On Thu, Mar 18, 2021 at 10:49 AM Leon Romanovsky <leon@kernel.org> wrote:
> >
> > No, I opened patch and added the note manually, so it is definitely my VIM.
> > Most likely this part of my .vimrc caused it.
>
> Ok, that would do it.
>
> Yeah, whitespace is easy to "fix" at patch application time, but it
> really is meaningful and you never should change whitespace for
> patches.
>
> Maybe you can limit your rules to just particular file types
> (although, honestly, I think it's bad for headers and C files too when
> it then causes entirely irrelevant and independent changes - you only
> want your own _new_ edits to be whitespace-clean, not fix other random
> issues).
>
> Better yet, maybe not "fix whitespace" at all, but have some code
> coloring logic that just points out bad whitespace? I use "git diff"
> myself, with colorization being default for tty operations:
>
> [color]
> ui=auto
>
> so that then "git diff" will show you your (new) evil whitespace
> errors when you review your changes, but won't complain about existing
> whitespace issues..
Yeah, my color.ui is "always", so I will simply remove the problematic
line from VIM and won't change whitespaces at all.
Thanks
>
> Linus
prev parent reply other threads:[~2021-03-20 11:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 10:45 [PATCH master] module: remove never implemented MODULE_SUPPORTED_DEVICE Leon Romanovsky
2021-03-17 20:17 ` Linus Torvalds
2021-03-18 7:55 ` Leon Romanovsky
2021-03-18 17:36 ` Linus Torvalds
2021-03-18 17:49 ` Leon Romanovsky
2021-03-18 17:55 ` Linus Torvalds
2021-03-20 9:23 ` Leon Romanovsky [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=YFW++S+TTCK/3dfO@unreal \
--to=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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