[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <F0C0E942-BA61-4C74-860B-93D57C3D0F9A@goldelico.com>
Date: Sat, 9 Apr 2022 15:57:02 +0200
From: "H. Nikolaus Schaller" <hns@...delico.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: Rob Herring <robh+dt@...nel.org>,
Paul Cercueil <paul@...pouillou.net>,
Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
linux-mips@...r.kernel.org, letux-kernel@...nphoenux.org
Subject: Re: [PATCH 05/18] MIPS: DTS: jz4780: fix pinctrl as reported by
dtbscheck
> Am 09.04.2022 um 15:46 schrieb Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>:
>
> On 09/04/2022 15:41, H. Nikolaus Schaller wrote:
>>>
>>> No. I ask you to fix all pin-controller cases, for entire MIPS, not just
>>> one.
>>
>> Oops. Nope. I am a volunteer and neither your employee nor slave.
>
> No one thinks differently and I am sorry that you felt it. Please accept
> my apologies, if you get different impression. You understand though the
> meaning of word "ask for something" and "order something" (the latter
> which I did not use).
>
> I just asked.
Ok. Maybe english is not our mother language and we sometimes don't
get the nuances right. Sorry if I understood that wrongly.
At least I now understand what you did suggest.
Doing the same change for treewide MIPS is beyond my capabilities since
I can't easily test any compile setup. So far I only compile for CI20 and
as far as I know every machine still needs its own config for MIPS
(haven't checked recently). So I am not even sure if dtbscheck tells me
all locations.
BR and thanks,
Nikolaus
Powered by blists - more mailing lists