public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Kever Yang <kever.yang@rock-chips.com>,
	Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-rockchip@lists.infradead.org,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Heiko Stuebner" <heiko.stuebner@cherry.de>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Neil Armstrong" <neil.armstrong@linaro.org>,
	"Rafał Miłecki" <rafal@milecki.pl>,
	"Rob Herring" <robh@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: vendor-prefixes: Update rockchip company name
Date: Mon, 09 Dec 2024 11:03:08 +0100	[thread overview]
Message-ID: <10907239.zapYfy813O@diego> (raw)
In-Reply-To: <kwx76ihsftsgw3u53l33z4kodihyfcvpqpl2a2nk7aedgnr6e6@2324w7s7zmio>

Am Montag, 9. Dezember 2024, 10:42:50 CET schrieb Krzysztof Kozlowski:
> On Thu, Dec 05, 2024 at 04:22:58PM +0800, Kever Yang wrote:
> > Rockchip company name has update to below name since 2021:
> > Rockchip Electronics Co., Ltd.
> 
> Some reference would be useful. Wikipedia says:
> Fuzhou Rockchip Electronics Co., Ltd.

I did go digging a bit:

their main english page [0] at the very bottom (in "very readable"
light gray on dark-grey ;-) ) says:
  "Rockchip Electronics Co., Ltd. All rights reserved"

Similarly their about-page [1] says:
  "Rockchip Electronics Co., Ltd. ("Rockchip", stock code: 603893)
   established in 2001 ..."


Heiko

[0] https://www.rock-chips.com/a/en/index.html
[1] https://www.rock-chips.com/a/en/About_Rockchip/About_Rockchip/index.html



  reply	other threads:[~2024-12-09 10:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-05  8:22 [PATCH] dt-bindings: vendor-prefixes: Update rockchip company name Kever Yang
2024-12-09  9:42 ` Krzysztof Kozlowski
2024-12-09 10:03   ` Heiko Stübner [this message]
2024-12-10  9:31     ` Krzysztof Kozlowski
     [not found]   ` <5a869ce4-b1ef-4308-a8ad-4252d8a7e5e3@rock-chips.com>
2024-12-10  7:24     ` Krzysztof Kozlowski
2025-02-10 11:02 ` Heiko Stuebner

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=10907239.zapYfy813O@diego \
    --to=heiko@sntech.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko.stuebner@cherry.de \
    --cc=kever.yang@rock-chips.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=neil.armstrong@linaro.org \
    --cc=rafal@milecki.pl \
    --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