public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Zhu Ling <1536943441@qq.com>,
	linux-gpio@vger.kernel.org, devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linus.walleij@linaro.org,
	brgl@bgdev.pl, andy@kernel.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
	chenbaozi@phytium.com.cn
Subject: Re: [PATCH v1 1/3] dt-bindings: gpio: add Phytium GPIO controller
Date: Tue, 3 Mar 2026 09:28:58 +0100	[thread overview]
Message-ID: <8fcf8766-a262-4eba-bfcf-c64dba1befb9@kernel.org> (raw)
In-Reply-To: <tencent_0BC92A632DD26F0A684E608D427244637905@qq.com>

On 02/03/2026 10:51, Zhu Ling wrote:
> Add the devicetree binding schema for the Phytium platform GPIO
> controller.
> 
> Register the "phytium" vendor prefix used by the compatible string.
> 
> Use ngpios as the preferred child-node property and keep nr-gpios as
> deprecated for compatibility with existing firmware descriptions.
> 

You Cc-ed inactive address, not existing in the kernel for like 2 years,
so clearly this was based on some old kernel.

No, you must work on mainline, not two years old stuff.

Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC (and consider --no-git-fallback argument, so you will
not CC people just because they made one commit years ago). It might
happen, that command when run on an older kernel, gives you outdated
entries. Therefore please be sure you base your patches on recent Linux
kernel.

Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline) or work on fork of kernel
(don't, instead use mainline). Just use b4 and everything should be
fine, although remember about `b4 prep --auto-to-cc` if you added new
patches to the patchset.

Best regards,
Krzysztof

  parent reply	other threads:[~2026-03-03  8:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260302095147.2483-1-1536943441@qq.com>
2026-03-02  9:51 ` [PATCH v1 1/3] dt-bindings: gpio: add Phytium GPIO controller Zhu Ling
2026-03-03  6:49   ` Krzysztof Kozlowski
2026-03-03  8:28   ` Krzysztof Kozlowski [this message]
2026-03-02  9:51 ` [PATCH v1 2/3] gpio: add support for Phytium platform " Zhu Ling
2026-03-02 10:14   ` Andy Shevchenko
2026-03-23 14:34   ` Linus Walleij
2026-03-02  9:51 ` [PATCH v1 3/3] MAINTAINERS: add entry for Phytium platform GPIO driver Zhu Ling
2026-03-02 10:03   ` Andy Shevchenko

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=8fcf8766-a262-4eba-bfcf-c64dba1befb9@kernel.org \
    --to=krzk@kernel.org \
    --cc=1536943441@qq.com \
    --cc=andy@kernel.org \
    --cc=brgl@bgdev.pl \
    --cc=chenbaozi@phytium.com.cn \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.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