From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Niedermayr, BENEDIKT" <benedikt.niedermayr@siemens.com>,
"robh@kernel.org" <robh@kernel.org>
Cc: "rogerq@kernel.org" <rogerq@kernel.org>,
"tony@atomide.com" <tony@atomide.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v6 2/2] dt-bindings: memory-controllers: gpmc-child: add wait-pin polarity
Date: Wed, 5 Oct 2022 13:00:42 +0200 [thread overview]
Message-ID: <c97db3d3-ccb2-fef5-070c-901053e6e353@linaro.org> (raw)
In-Reply-To: <fc1d354d307487de2dc8e715c202affd76f96866.camel@siemens.com>
On 05/10/2022 12:13, Niedermayr, BENEDIKT wrote:
>>> diff --git a/Documentation/devicetree/bindings/memory-controllers/ti,gpmc-child.yaml b/Documentation/devicetree/bindings/memory-controllers/ti,gpmc-
>>> child.yaml
>>> index 6e3995bb1630..477189973334 100644
>>> --- a/Documentation/devicetree/bindings/memory-controllers/ti,gpmc-child.yaml
>>> +++ b/Documentation/devicetree/bindings/memory-controllers/ti,gpmc-child.yaml
>>> @@ -230,6 +230,13 @@ properties:
>>> Wait-pin used by client. Must be less than "gpmc,num-waitpins".
>>> $ref: /schemas/types.yaml#/definitions/uint32
>>>
>>> + gpmc,wait-pin-polarity:
>>
>> 'gpmc' is not a vendor. Don't continue this bad pattern, use 'ti'.
>
> You are right. But nevertheless I can't agree with that in this patch series.
> I don't want to break consistency, since all bindings currently use 'gpmc'. At least this applies
> to the "ti,gpmc-child.yaml".
>
> I think it makes more sense to create a complete new patch series for that specific change? This change
> wouldn't fit thematically the current patch series.
>
So you want to add new property incorrectly named and immediately new
patch which fixes the name? No, please squash this new patch into this.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-10-05 11:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 12:56 [PATCH v6 0/2] gpmc wait pin additions B. Niedermayr
2022-09-29 12:56 ` [PATCH v6 1/2] memory: omap-gpmc: " B. Niedermayr
2022-10-01 9:18 ` Roger Quadros
2022-09-29 12:56 ` [PATCH v6 2/2] dt-bindings: memory-controllers: gpmc-child: add wait-pin polarity B. Niedermayr
2022-09-30 19:42 ` Rob Herring
2022-09-30 20:01 ` Krzysztof Kozlowski
2022-10-05 10:05 ` Niedermayr, BENEDIKT
2022-10-05 11:01 ` Krzysztof Kozlowski
2022-10-05 10:13 ` Niedermayr, BENEDIKT
2022-10-05 11:00 ` Krzysztof Kozlowski [this message]
2022-10-05 11:15 ` Niedermayr, BENEDIKT
2022-10-05 11:48 ` Krzysztof Kozlowski
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=c97db3d3-ccb2-fef5-070c-901053e6e353@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=benedikt.niedermayr@siemens.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=tony@atomide.com \
/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).