Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   =?utf-8?Q?Krzysztof_Ha=C5=82asa?= <khalasa@piap.pl>
To:     Laurent Pinchart <laurent.pinchart@ideasonboard.com>
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
References: <m3y2b25er8.fsf@t19.piap.pl>
        <YNHVbFp2+Ow8CyCV@pendragon.ideasonboard.com>
Sender: khalasa@piap.pl
Date:   Wed, 23 Jun 2021 07:46:25 +0200
In-Reply-To: <YNHVbFp2+Ow8CyCV@pendragon.ideasonboard.com> (Laurent Pinchart's
        message of "Tue, 22 Jun 2021 15:19:56 +0300")
Message-ID: <m3im255e1a.fsf@t19.piap.pl>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

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.
--=20
Krzysztof Ha=C5=82asa

Sie=C4=87 Badawcza =C5=81ukasiewicz
Przemys=C5=82owy Instytut Automatyki i Pomiar=C3=B3w PIAP
Al. Jerozolimskie 202, 02-486 Warszawa