From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: "Krzysztof Hałasa" <khalasa@piap.pl>
Cc: devicetree@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC v2] dt-binding: media: document ON Semi AR0521 sensor bindings
Date: Wed, 23 Jun 2021 16:21:21 +0300 [thread overview]
Message-ID: <YNM1UeZ7aw0hWUE2@pendragon.ideasonboard.com> (raw)
In-Reply-To: <m3im255e1a.fsf@t19.piap.pl>
On Wed, Jun 23, 2021 at 07:46:25AM +0200, Krzysztof Hałasa wrote:
> Laurent Pinchart <laurent.pinchart@ideasonboard.com> writes:
>
> >> The question still stands: is there a way to reliably put national
> >> unicode characters into:
> >> - commit messages for patches submitted via email,
> >
> > This shouldn't be too much of a problem, as long as you MUA and MTA
> > don't mess up encoding.
>
> Maybe it's better now. I had mixed results in the past, but maybe it was
> 10+ years ago. Then I stopped using non-ASCII as they weren't very
> essential.
> Apparently there was no such problems with drivers/net, at least from
> the time I started using non-ASCII characters.
I think it should be better, yes. As long as there's no MS Exchange
along the way of course ;-)
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2021-06-23 13:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 11:18 [RFC v2] dt-binding: media: document ON Semi AR0521 sensor bindings Krzysztof Hałasa
2021-06-22 12:19 ` Laurent Pinchart
2021-06-23 5:46 ` Krzysztof Hałasa
2021-06-23 13:21 ` Laurent Pinchart [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=YNM1UeZ7aw0hWUE2@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=devicetree@vger.kernel.org \
--cc=khalasa@piap.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.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