Linux-Aspeed Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kevin Chen <kevin_chen@aspeedtech.com>,
	"joel@jms.id.au" <joel@jms.id.au>,
	"andrew@codeconstruct.com.au" <andrew@codeconstruct.com.au>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"elbadrym@google.com" <elbadrym@google.com>
Subject: Re: [PATCH v0 1/3] dt-binding: aspeed: Add LPC PCC controller
Date: Mon, 17 Feb 2025 12:55:27 +0100	[thread overview]
Message-ID: <78dc2cee-2d87-42a9-8e0b-2199c653def4@kernel.org> (raw)
In-Reply-To: <PSAPR06MB4949CB5CE2E08B98B368160589FF2@PSAPR06MB4949.apcprd06.prod.outlook.com>

On 13/02/2025 09:46, Kevin Chen wrote:
>> On 17/01/2025 10:52, Kevin Chen wrote:
>>> Add dt-bindings for Aspeed for Aspeed LPC POST code capture controller.
>>>
>>> Signed-off-by: Kevin Chen <kevin_chen@aspeedtech.com>
>>> ---
>>
>> Patchsets start from 1, not 0.
> Agree, I will resend the patchsets of v1.
> 
>>
>> This wasn't tested as it has obvious errors, so no review. Test your patches
>> before you send them.
> Agree, I will run "make dtbs_check W=1" and " make dt_binding_check " to check result is clean before the next commits.
> 
>>
>>
>> <form letter>
>> Please use scripts/get_maintainers.pl to get a list of necessary people and lists
>> to CC. It might happen, that command when run on an older kernel, gives you
>> outdated entries. Therefore please be sure you base your patches on recent
>> Linux kernel.
>>
>> Tools like b4 or scripts/get_maintainer.pl provide you proper list of people, so
>> fix your workflow. Tools might also fail if you work on some ancient tree (don't,
>> instead use mainline) or work on fork of kernel (don't, instead use mainline).
>> Just use b4 and everything should be fine, although remember about `b4 prep
>> --auto-to-cc` if you added new patches to the patchset.
>>
>> You missed at least devicetree list (maybe more), so this won't be tested by
>> automated tooling. Performing review on untested code might be a waste of
>> time.
>>
>> Please kindly resend and include all necessary To/Cc entries.
>> </form letter>

How did you implement this feedback?

Best regards,
Krzysztof


  reply	other threads:[~2025-02-17 11:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-17  9:52 [PATCH v0 0/3] Add AST2600 LPC PCC support Kevin Chen
2025-01-17  9:52 ` [PATCH v0 1/3] dt-binding: aspeed: Add LPC PCC controller Kevin Chen
2025-01-18  8:19   ` Krzysztof Kozlowski
2025-02-13  8:46     ` Kevin Chen
2025-02-17 11:55       ` Krzysztof Kozlowski [this message]
2025-02-18 11:05         ` Kevin Chen
2025-02-18 11:32           ` Krzysztof Kozlowski
2025-01-17  9:52 ` [PATCH v0 2/3] ARM: dts: aspeed-g6: Add AST2600 LPC PCC support Kevin Chen
2025-01-17  9:52 ` [PATCH v0 3/3] soc: aspeed: lpc-pcc: Add PCC controller support Kevin Chen
2025-01-18  8:24   ` Krzysztof Kozlowski
2025-02-13  8:57     ` Kevin Chen
2025-01-17 14:32 ` [PATCH v0 0/3] Add AST2600 LPC PCC support Rob Herring (Arm)

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=78dc2cee-2d87-42a9-8e0b-2199c653def4@kernel.org \
    --to=krzk@kernel.org \
    --cc=andrew@codeconstruct.com.au \
    --cc=elbadrym@google.com \
    --cc=joel@jms.id.au \
    --cc=kevin_chen@aspeedtech.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.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