[PATCH v3 0/3] pinctrl: pinctrl-zynqmp: Add Versal platform support

[Krzysztof Kozlowski]

On 05/08/2024 10:58, Potthuri, Sai Krishna wrote:
> Hi Krzysztof,
> 
>> -----Original Message-----
>> From: Krzysztof Kozlowski <krzysztof.kozlowski at linaro.org>
>> Sent: Sunday, August 4, 2024 8:20 PM
>> To: Potthuri, Sai Krishna <sai.krishna.potthuri at amd.com>; Linus Walleij
>> <linus.walleij at linaro.org>; Simek, Michal <michal.simek at amd.com>; Rob
>> Herring <robh+dt at kernel.org>; Krzysztof Kozlowski
>> <krzysztof.kozlowski+dt at linaro.org>; Conor Dooley <conor+dt at kernel.org>;
>> Buddhabhatti, Jay <jay.buddhabhatti at amd.com>; Kundanala, Praveen Teja
>> <praveen.teja.kundanala at amd.com>; Greg Kroah-Hartman
>> <gregkh at linuxfoundation.org>
>> Cc: linux-arm-kernel at lists.infradead.org; linux-kernel at vger.kernel.org;
>> linux-gpio at vger.kernel.org; devicetree at vger.kernel.org;
>> saikrishna12468 at gmail.com; git (AMD-Xilinx) <git at amd.com>
>> Subject: Re: [PATCH v3 0/3] pinctrl: pinctrl-zynqmp: Add Versal platform
>> support
>>
>> On 01/08/2024 14:00, Sai Krishna Potthuri wrote:
>>> Update the binding and pinctrl-zynqmp driver to add Versal platform
>>> support.
>>> Add Get Attribute ID in the Xilinx firmware driver to get the pin
>>> information from Xilinx Platform Management Firmware.
>>
>> Any particular reason why you are developing patches on some quite old
>> kernel?
> I created this patch series on top of latest Pin control subsystem tree(Linus Walleij),
> 'for-next' branch.

I have doubts... otherwise get_maintainers.pl would point different
address. Assuming you indeed use for-next branch, then sending process
is wrong - you use some unusual commands instead of expected
get_maintainers.pl or b4.

Best regards,
Krzysztof