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: Thu, 18 Mar 2021 19:49:25 +0200 [thread overview]
Message-ID: <YFOSpQcrfP1UvqoL@unreal> (raw)
In-Reply-To: <CAHk-=wgdHxuQmhKR9oAS5bhahmo5CFj3x6YdHVPBCGhbSz6rEg@mail.gmail.com>
On Thu, Mar 18, 2021 at 10:36:36AM -0700, Linus Torvalds wrote:
> On Thu, Mar 18, 2021 at 12:55 AM Leon Romanovsky <leon@kernel.org> wrote:
> > >
> > > Also, your email seems to have swallowed spaces at the ends of lines.
> > >
> > > I can (and did) apply the patch with "--whitespace=fix", but that then
> > > causes git to fix some _other_ whitespace too, so the end result isn't
> > > quite the same. Oh well.
> > >
> > > Please check what's up with your email sending client that it seems to
> > > remove space at end of lines in patches.
> >
> > This is strange, I'm sending patches with "git send-email" with pretty
> > standard settings:
>
> Hmm. I can't tell whats' wrong, but both my own mailbox and the
> lore.kernel.org clearly has missing whitespace at end of lines.
>
> You can see it yourself with a simple
>
> b4 am 20210317104547.442203-1-leon@kernel.org
>
> (assuming you have b4 installed, of course:
>
> https://pypi.org/project/b4/
>
> but with a kernel.org address I'm sure you've seen the emails about it
> even if you may not be a user).
Thanks, I'll try.
>
> > Also, I'm using mail.kernel.org as a SMTP especially to make sure that
> > my mails are not mangled by our exchange server.
>
> Yeah, the email looks fine in any other way technically, it passes SPF
> and DKIM, and I don't see anything else strange going on either.
>
> I think the same VIM issue that caused some whitespace line changes
> for you in the patch might have then bitten you when you sent it out -
> I know you must have edited the message, becasuse you have that
>
> "I'm sending this patch to you directly because it is much saner to
> apply it in one place instead of multiple patches saga that will [...]"
>
> below the commit message, that you presumable added with "--annotate".
No, I opened patch and added the note manually, so it is definitely my VIM.
Most likely this part of my .vimrc caused it.
" Remove trailing white spaces
" http://vim.wikia.com/wiki/Remove_unwanted_spaces
autocmd BufWritePre * %s/\s\+$//e
>
> > Are you sure that such change came from me and not from "--whitespace=fix"?
>
> Yup. See above on how you can just use b4 to download a copy yourself..
I'll try, thanks for taking the patch and for the analysis.
>
> Linus
next prev parent reply other threads:[~2021-03-18 17:50 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 [this message]
2021-03-18 17:55 ` Linus Torvalds
2021-03-20 9:23 ` Leon Romanovsky
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=YFOSpQcrfP1UvqoL@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