devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: kris@embeddedTS.com, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Mark Featherston <mark@embeddedTS.com>
Subject: Re: [PATCH] ARM: dts: imx6qdl-ts7970: Fix ngpio typo and count
Date: Thu, 30 Jun 2022 21:27:24 +0200	[thread overview]
Message-ID: <51cb7b8b-9616-35b1-cd34-e054dd98369c@linaro.org> (raw)
In-Reply-To: <1656616263.4126.2.camel@embeddedTS.com>

On 30/06/2022 21:11, Kris Bahnsen wrote:
> On Thu, 2022-06-30 at 20:56 +0200, Krzysztof Kozlowski wrote:
>> On 30/06/2022 20:27, Kris Bahnsen wrote:
>>> Device-tree incorrectly used "ngpio" which caused the driver to
>>> fallback to 32 ngpios.
>>>
>>> This platform has 62 GPIO registers.
>>>
>>> Signed-off-by: Kris Bahnsen <kris@embeddedTS.com>
>>> ---
>>
>>
>> Ah and one more - for some reason you did not send it to maintainers, so
>> patch will be most likely ignored. Please use scripts/get_maintainer.pl
>> to CC relevant people.
> 
> I reviewed that output and erred on the side of not generating
> too much noise and skipped folks/lists marked as general ARM/NXP
> maintainers. I'll be sure to send to all in the future.

For small patchsets usually entire output of get_maintainers.pl is
correct. What's worth to skip are the entries coming from history
(--no-git-fallback).

Best regards,
Krzysztof

      reply	other threads:[~2022-06-30 19:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30 18:27 [PATCH] ARM: dts: imx6qdl-ts7970: Fix ngpio typo and count Kris Bahnsen
2022-06-30 18:55 ` Krzysztof Kozlowski
2022-06-30 18:56 ` Krzysztof Kozlowski
2022-06-30 19:11   ` Kris Bahnsen
2022-06-30 19:27     ` Krzysztof Kozlowski [this message]

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=51cb7b8b-9616-35b1-cd34-e054dd98369c@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kris@embeddedTS.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@embeddedTS.com \
    --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;
as well as URLs for NNTP newsgroup(s).