From: Jianfeng Liu <liujianfeng1994@gmail.com>
To: krzk@kernel.org
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, heiko@sntech.de,
krzk+dt@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
liujianfeng1994@gmail.com, robh@kernel.org, sfr@canb.auug.org.au,
weizhao.ouyang@arm.com
Subject: Re: Re: [PATCH v2 1/3] dt-bindings: vendor-prefixes: add ArmSoM
Date: Mon, 15 Apr 2024 16:54:19 +0800 [thread overview]
Message-ID: <20240415085419.6107-1-liujianfeng1994@gmail.com> (raw)
In-Reply-To: <dcda2991-90bc-41eb-afa3-14a2071a6d19@kernel.org>
Hi Krzysztof,
On Mon, 15 Apr 2024 10:04:14 +0200, Krzysztof Kozlowski wrote:
>> Add vendor prefix for ArmSoM (https://www.armsom.org)
>
>I feel some lawsuits coming...
The brand name "ArmSoM" was first registered on 10 December 2021, which
means "System-on-Module of ARM". Would you please explan it further
about the risk of law? We are working with ARM for the SystemReady
certification.
>Website says different name. Please use name from the website.
Sure, I will change it to "ArmSoM Technology Co., Ltd." in v3.
Best regards,
Jianfeng
next prev parent reply other threads:[~2024-04-15 8:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-13 15:36 [PATCH v2 0/3] Add ArmSom Sige7 board Jianfeng Liu
2024-04-13 15:36 ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: add ArmSoM Jianfeng Liu
2024-04-15 8:04 ` Krzysztof Kozlowski
2024-04-15 8:54 ` Jianfeng Liu [this message]
2024-04-13 15:36 ` [PATCH v2 2/3] dt-bindings: arm: rockchip: Add ArmSoM Sige7 Jianfeng Liu
2024-04-15 7:59 ` Krzysztof Kozlowski
2024-04-13 15:36 ` [PATCH v2 3/3] arm64: dts: rockchip: Add ArmSom Sige7 board Jianfeng Liu
2024-04-15 18:46 ` [PATCH v2 0/3] " Rob Herring
2024-04-16 3:01 ` Jianfeng Liu
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=20240415085419.6107-1-liujianfeng1994@gmail.com \
--to=liujianfeng1994@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=weizhao.ouyang@arm.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).