From: Conor Dooley <conor@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] docs: dt: writing-bindings: Rephrase typical fallback (superset) usage
Date: Mon, 7 Jul 2025 16:00:00 +0100 [thread overview]
Message-ID: <20250707-camper-postwar-2ea9e6faa8dc@spud> (raw)
In-Reply-To: <20250707095019.66792-4-krzysztof.kozlowski@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 480 bytes --]
On Mon, Jul 07, 2025 at 11:50:20AM +0200, Krzysztof Kozlowski wrote:
> When speaking about compatibles for new devices comparing to "prior
> implementations", usually we expect new device to come with more
> features, thus logically it is a superset, not subset, of "prior
> implementations".
>
> Suggested-by: Conor Dooley <conor@kernel.org>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-07-07 15:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 9:50 [PATCH v2 1/3] docs: dt: writing-bindings: Rephrase typical fallback (superset) usage Krzysztof Kozlowski
2025-07-07 9:50 ` [PATCH v2 2/3] docs: dt: writing-bindings: Express better expectations of "specific" Krzysztof Kozlowski
2025-07-07 15:00 ` Conor Dooley
2025-07-08 12:22 ` Rob Herring (Arm)
2025-07-07 9:50 ` [PATCH v2 3/3] docs: dt: writing-bindings: Consistently use single-whitespace Krzysztof Kozlowski
2025-07-07 15:01 ` Conor Dooley
2025-07-08 12:22 ` Rob Herring (Arm)
2025-07-07 15:00 ` Conor Dooley [this message]
2025-07-08 12:20 ` [PATCH v2 1/3] docs: dt: writing-bindings: Rephrase typical fallback (superset) usage Rob Herring (Arm)
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=20250707-camper-postwar-2ea9e6faa8dc@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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