Devicetree
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Chukun Pan <amadeus@jmu.edu.cn>
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,
	robh@kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: arm: rockchip: Add MangoPi M28K
Date: Tue, 4 Aug 2026 08:45:37 +0200	[thread overview]
Message-ID: <9de52b72-ce95-440e-8178-461157a157d1@kernel.org> (raw)
In-Reply-To: <20260804064000.1047278-1-amadeus@jmu.edu.cn>

On 04/08/2026 08:40, Chukun Pan wrote:
> Hi,
> 
>> How did you resolve my comments from v1? You split patches instead of
>> squashing and removed any explanation I asked for.
> 
> My idea is to add an official product link to differentiate them.
> HINLINK H28K has this link, which I added to the commit message.
> As for MangoPi, since it's discontinued, there's no product link
> available. I will include a link to an image of the board in the
> next patch to show that they are different boards.
> 
> Does this solve your problem?

I asked you to squash the patches, to avoid work. Instead, you split the
patchsets giving us more work.

Best regards,
Krzysztof

  reply	other threads:[~2026-08-04  6:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-01  8:00 [PATCH v2 0/2] arm64: dts: rockchip: Add MangoPi M28K Chukun Pan
2026-08-01  8:00 ` [PATCH v2 1/2] dt-bindings: arm: " Chukun Pan
2026-08-03  9:34   ` Krzysztof Kozlowski
2026-08-04  6:40     ` Chukun Pan
2026-08-04  6:45       ` Krzysztof Kozlowski [this message]
2026-08-04 11:50         ` Chukun Pan
2026-08-05  7:22   ` Krzysztof Kozlowski
2026-08-01  8:00 ` [PATCH v2 2/2] arm64: dts: " Chukun Pan
2026-08-01  8:13   ` sashiko-bot

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=9de52b72-ce95-440e-8178-461157a157d1@kernel.org \
    --to=krzk@kernel.org \
    --cc=amadeus@jmu.edu.cn \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=krzk+dt@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 \
    /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