Devicetree
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: "JiaLong.Yang" <jialong.yang@shingroup.cn>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	shenghui.qu@shingroup.cn, linux-kernel@vger.kernel.org,
	Rob Herring <robh@kernel.org>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Support uncore NI-700 Performance Monitor
Date: Fri, 3 May 2024 14:11:49 +0100	[thread overview]
Message-ID: <20240503131148.GC18392@willie-the-truck> (raw)
In-Reply-To: <cover.1709694173.git.jialong.yang@shingroup.cn>

On Wed, Mar 06, 2024 at 02:16:00PM +0800, JiaLong.Yang wrote:
> 1. 
> The MAINTAINERS file should be in dt-bindings or drivers?
> It's needed by the two subpatchs.
> I place it in dt-bindings. So I receive the warning in driver patch.
> 
> 2.
> When using the new macro DEFINE_FREE(), we should ended it without ';'.
> So there is one warning asking me to indentation next statement.
> 
> 3.
> If the file vendor-prefixes.yaml should be submit solely?
> 
> JiaLong.Yang (3):
>   dt-bindings: Add HEXIN Technologies Co., Ltd. vendor prefix
>   dt-bindings: perf: Support uncore NI-700 PMU
>   perf/hx_arm_ni: Support uncore NI-700 PMU

Please can you take a look at Robin's series for this IP?

https://lore.kernel.org/r/cover.1713972897.git.robin.murphy@arm.com

Thanks,

Will

      parent reply	other threads:[~2024-05-03 13:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06  6:16 [PATCH v3 0/2] Support uncore NI-700 Performance Monitor JiaLong.Yang
2024-03-06  6:16 ` [PATCH v3 0/2] dt-bindings: Add HEXIN Technologies Co., Ltd. vendor prefix JiaLong.Yang
2024-03-06  6:16   ` [PATCH v3 1/2] dt-bindings: perf: Support uncore NI-700 PMU JiaLong.Yang
2024-03-06 21:46     ` Rob Herring
2024-03-07  6:33       ` Yang Jialong 杨佳龙
2024-03-06  7:10   ` [PATCH v3 0/2] dt-bindings: Add HEXIN Technologies Co., Ltd. vendor prefix Krzysztof Kozlowski
2024-03-06  7:19     ` Yang Jialong 杨佳龙
2024-05-03 13:11 ` Will Deacon [this message]

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=20240503131148.GC18392@willie-the-truck \
    --to=will@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jialong.yang@shingroup.cn \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=shenghui.qu@shingroup.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