From: Sui Jingfeng <15330273260@189.cn>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Roland Scheidegger <sroland@vmware.com>,
Zack Rusin <zackr@vmware.com>,
Christian Gmeiner <christian.gmeiner@gmail.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Rob Herring <robh+dt@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Dan Carpenter <dan.carpenter@oracle.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Andrey Zhizhikin <andrey.zhizhikin@leica-geosystems.com>,
Sam Ravnborg <sam@ravnborg.org>,
"David S . Miller" <davem@davemloft.net>,
Lucas Stach <l.stach@pengutronix.de>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Ilia Mirkin <imirkin@alum.mit.edu>,
Qing Zhang <zhangqing@loongson.cn>,
suijingfeng <suijingfeng@loongson.cn>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v10 1/4] MIPS: Loongson64: dts: update the display controller device node
Date: Mon, 21 Feb 2022 09:27:49 +0800 [thread overview]
Message-ID: <034c425e-bcd8-0fe4-f10c-3ef297ffcc72@189.cn> (raw)
In-Reply-To: <a865b770-126e-a7c0-48bb-4f072b8dc5bd@flygoat.com>
On 2022/2/21 02:18, Jiaxun Yang wrote:
>
>
> 在 2022/2/20 14:55, Sui Jingfeng 写道:
>> From: suijingfeng <suijingfeng@loongson.cn>
>>
>> The display controller is a pci device, its PCI vendor id is 0x0014
>> its PCI device id is 0x7a06.
>>
>> 1) In order to let the driver to know which chip the DC is contained
>> in, the compatible string of the display controller is updated
>> according to the chip's name.
>>
>> 2) Add display controller device node for ls2k1000 SoC
>>
>> Reported-by: Krzysztof Kozlowski <krzk@kernel.org>
> ^ The usage of Reported-by flag seems wired here.
> In most case we use it to credit people who find a bug that is already
> in-tree.
> Reviewing effort is already credited by Reviewed-by flag.
>
> If you intend to let maintainers track their suggestions easier, the
> common
> practice is to append suggester's name after each entry of changelog
> between versions.
>
> Thanks.
Ok, Now I know that. I will revise it next time, thank you.
>
>> Signed-off-by: suijingfeng <suijingfeng@loongson.cn>
>> Signed-off-by: Sui Jingfeng <15330273260@189.cn>
>> ---
>> arch/mips/boot/dts/loongson/loongson64-2k1000.dtsi | 8 ++++++++
>> arch/mips/boot/dts/loongson/ls7a-pch.dtsi | 7 ++-----
>> 2 files changed, 10 insertions(+), 5 deletions(-)
>>
> [...]
> - Jiaxun
next prev parent reply other threads:[~2022-02-21 1:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-20 14:55 [PATCH v10 0/4] drm/lsdc: add drm driver for loongson display controller Sui Jingfeng
2022-02-20 14:55 ` [PATCH v10 1/4] MIPS: Loongson64: dts: update the display controller device node Sui Jingfeng
2022-02-20 18:18 ` Jiaxun Yang
2022-02-21 1:27 ` Sui Jingfeng [this message]
2022-02-21 9:19 ` Sergei Shtylyov
2022-02-21 10:01 ` Krzysztof Kozlowski
2022-02-21 13:57 ` Sui Jingfeng
2022-02-21 13:53 ` Sui Jingfeng
2022-02-20 14:55 ` [PATCH v10 2/4] Documentation/dt: Add descriptions for loongson display controller Sui Jingfeng
2022-02-20 18:22 ` Jiaxun Yang
2022-02-21 7:31 ` Krzysztof Kozlowski
2022-02-22 23:02 ` Rob Herring
2022-02-23 13:56 ` 隋景峰
2022-02-23 15:35 ` Sui Jingfeng
2022-02-23 15:44 ` Krzysztof Kozlowski
2022-02-23 15:40 ` Krzysztof Kozlowski
2022-02-20 14:55 ` [PATCH v10 4/4] MAINTAINERS: add maintainers for DRM LSDC driver Sui Jingfeng
[not found] ` <20220220145554.117854-4-15330273260@189.cn>
2022-02-22 8:27 ` [PATCH v10 3/4] drm/lsdc: add drm driver for loongson display controller Maxime Ripard
2022-02-22 13:53 ` Sui Jingfeng
2022-02-22 14:46 ` Sui Jingfeng
2022-02-23 14:39 ` Maxime Ripard
2022-02-23 15:14 ` Sui Jingfeng
2022-02-23 15:41 ` Maxime Ripard
2022-02-23 15:45 ` Sui Jingfeng
2022-02-23 12:47 ` kernel test robot
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=034c425e-bcd8-0fe4-f10c-3ef297ffcc72@189.cn \
--to=15330273260@189.cn \
--cc=airlied@linux.ie \
--cc=andrey.zhizhikin@leica-geosystems.com \
--cc=christian.gmeiner@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=daniel@ffwll.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=imirkin@alum.mit.edu \
--cc=jiaxun.yang@flygoat.com \
--cc=krzk@kernel.org \
--cc=l.stach@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=sroland@vmware.com \
--cc=suijingfeng@loongson.cn \
--cc=tsbogend@alpha.franken.de \
--cc=tzimmermann@suse.de \
--cc=zackr@vmware.com \
--cc=zhangqing@loongson.cn \
/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).