From: Esben Haabendal <esben@geanix.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
Jessica Zhang <quic_jesszhan@quicinc.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>,
Daniel Vetter <daniel@ffwll.ch>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: vendor-prefixes: Add JMO Tech
Date: Wed, 14 Aug 2024 17:27:56 +0200 [thread overview]
Message-ID: <87wmkj3z0j.fsf@geanix.com> (raw)
In-Reply-To: <97f60cd3-1433-4dc5-9dc4-ad9a53c1b35a@kernel.org> (Krzysztof Kozlowski's message of "Wed, 14 Aug 2024 17:26:49 +0200")
Krzysztof Kozlowski <krzk@kernel.org> writes:
> On 14/08/2024 16:43, Esben Haabendal wrote:
>> Krzysztof Kozlowski <krzk@kernel.org> writes:
>>
>>> On 14/08/2024 15:10, Esben Haabendal wrote:
>>>> Add vendor prefix for JMO Tech CO., LTD. (http://www.jmolcd.com/).
>>>>
>>>> Signed-off-by: Esben Haabendal <esben@geanix.com>
>>>> ---
>>>> Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
>>>> 1 file changed, 2 insertions(+)
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml
>>>> index a70ce43b3dc0..5d2ada6cfa61 100644
>>>> --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
>>>> +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
>>>> @@ -758,6 +758,8 @@ patternProperties:
>>>> description: Jiandangjing Technology Co., Ltd.
>>>> "^jide,.*":
>>>> description: Jide Tech
>>>> + "^jmo,.*":
>>>
>>> Wevsite is jmolcd, so prefix should match it - jmolcd.
>>
>> Ok. Even though the companies name is "JMO Tech CO.,LTD", and does not
>> hint at "jmolcd"?
>
> We use domain names as vendor prefixes, so when another "jmo.com" comes,
> they will get "jmo", not something else.
Ok. I will change it for v2 of the series.
/Esben
next prev parent reply other threads:[~2024-08-14 15:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 13:10 [PATCH 0/3] drm/panel: ili9881c: Add JMO LCM-JM800WX support Esben Haabendal
2024-08-14 13:10 ` [PATCH 1/3] dt-bindings: vendor-prefixes: Add JMO Tech Esben Haabendal
2024-08-14 14:25 ` Krzysztof Kozlowski
2024-08-14 14:43 ` Esben Haabendal
2024-08-14 15:26 ` Krzysztof Kozlowski
2024-08-14 15:27 ` Esben Haabendal [this message]
2024-08-14 15:28 ` Krzysztof Kozlowski
2024-08-14 13:10 ` [PATCH 2/3] dt-bindings: ili9881c: Add JMO LCM-JM800WX LCD panel Esben Haabendal
2024-08-14 15:30 ` Krzysztof Kozlowski
2024-08-14 13:10 ` [PATCH 3/3] drm/panel: ili9881c: Add JMO LCM-JM800WX support Esben Haabendal
2024-09-24 9:53 ` Dmitry Baryshkov
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=87wmkj3z0j.fsf@geanix.com \
--to=esben@geanix.com \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_jesszhan@quicinc.com \
--cc=robh@kernel.org \
--cc=tzimmermann@suse.de \
/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).