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;
Date:   Wed, 23 Jun 2021 16:21:21 +0300
From:   Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To:     Krzysztof =?utf-8?Q?Ha=C5=82asa?= <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
Message-ID: <YNM1UeZ7aw0hWUE2@pendragon.ideasonboard.com>
References: <m3y2b25er8.fsf@t19.piap.pl>
 <YNHVbFp2+Ow8CyCV@pendragon.ideasonboard.com>
 <m3im255e1a.fsf@t19.piap.pl>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <m3im255e1a.fsf@t19.piap.pl>
Precedence: bulk

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