From: Wolfram Sang <wsa@the-dreams.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>
Subject: Re: linux-next: Fixes tag needs some work in the i2c tree
Date: Tue, 28 Apr 2020 09:01:30 +0200 [thread overview]
Message-ID: <20200428070130.GA2522@kunai> (raw)
In-Reply-To: <20200428082848.19d38b67@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 446 bytes --]
> This triggered because the "space" after the ":" is a Unicode non-breaking
> space (U+0x00a0, UTF8 0xc2 0xa0). I am not sure if this is a problem
> or not. This is the forst time I have seen this.
Thanks for reporting, I obviously didn't notice. Well, technically,
commit messages can be UTF8, so not really an error. However, it will
probably break lots of homebrew scripts, so a checkpatch warning it is,
then?
I'll fix it nonetheless.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-04-28 7:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 22:28 linux-next: Fixes tag needs some work in the i2c tree Stephen Rothwell
2020-04-28 7:01 ` Wolfram Sang [this message]
2020-04-28 8:41 ` Stephen Rothwell
2020-04-28 10:14 ` Wolfram Sang
-- strict thread matches above, loose matches on Subject: below --
2021-08-25 21:44 Stephen Rothwell
2021-08-17 21:52 Stephen Rothwell
2021-08-18 18:16 ` Sergey Shtylyov
2021-08-19 17:15 ` Wolfram Sang
2021-08-17 21:49 Stephen Rothwell
2021-08-18 17:28 ` Sergey Shtylyov
2021-08-19 17:15 ` Wolfram Sang
2019-10-24 20:07 Stephen Rothwell
2019-08-01 14:02 Stephen Rothwell
2019-08-01 20:21 ` Wolfram Sang
2019-04-23 21:55 Stephen Rothwell
2019-04-23 22:17 ` Wolfram Sang
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=20200428070130.GA2522@kunai \
--to=wsa@the-dreams.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rayagonda.kokatanur@broadcom.com \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).