From: Krzysztof Kozlowski <krzk@kernel.org>
To: Zhao Qunqin <zhaoqunqin@loongson.cn>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
chenhuacai@kernel.org, linux-edac@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@xen0n.name, bp@alien8.de, tony.luck@intel.com,
james.morse@arm.com, mchehab@kernel.org, rric@kernel.org,
loongarch@lists.linux.dev
Subject: Re: [PATCH V3 1/2] dt-bindings: EDAC for ls3a5000 memory controller
Date: Wed, 4 Sep 2024 07:51:12 +0200 [thread overview]
Message-ID: <c1508929-2e44-497d-b54a-285a3e74ba2d@kernel.org> (raw)
In-Reply-To: <32aded46-86ce-59cf-e8b4-2621c0dd9ebe@loongson.cn>
On 04/09/2024 03:15, Zhao Qunqin wrote:
>
> 在 2024/9/3 下午8:29, Krzysztof Kozlowski 写道:
>> On 03/09/2024 13:47, Zhao Qunqin wrote:
>>> add device tree bindings for ls3a5000 EDAC driver.
>>>
>>> Signed-off-by: Zhao Qunqin <zhaoqunqin@loongson.cn>
>> So no improvements? No changes? Why do you send the same?
>
> I'm sorry, I thought if you hadn't raised any issues with the previous
> version of dt binding, I wouldn't need to make any changes.
>
> For this version of the patch, I only changed the driver.
So what changed? Where is the changelog? Where is the tag? Did you get one?
Did you read submitting patches document?
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-09-04 5:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 11:47 [PATCH V3 0/2] Add EDAC driver for loongson memory controller Zhao Qunqin
2024-09-03 11:47 ` [PATCH V3 1/2] dt-bindings: EDAC for ls3a5000 " Zhao Qunqin
2024-09-03 12:29 ` Krzysztof Kozlowski
2024-09-04 1:15 ` Zhao Qunqin
2024-09-04 5:51 ` Krzysztof Kozlowski [this message]
2024-09-04 8:51 ` Zhao Qunqin
2024-09-03 11:47 ` [PATCH V3 2/2] Loongarch: EDAC driver for loongson " Zhao Qunqin
-- strict thread matches above, loose matches on Subject: below --
2024-09-03 11:46 [PATCH V3 0/2] Add " Zhao Qunqin
2024-09-03 11:46 ` [PATCH V3 1/2] dt-bindings: EDAC for ls3a5000 " Zhao Qunqin
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=c1508929-2e44-497d-b54a-285a3e74ba2d@kernel.org \
--to=krzk@kernel.org \
--cc=bp@alien8.de \
--cc=chenhuacai@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=james.morse@arm.com \
--cc=kernel@xen0n.name \
--cc=krzk+dt@kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=rric@kernel.org \
--cc=tony.luck@intel.com \
--cc=zhaoqunqin@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).