Devicetree
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Leng Honglin <lenghonglin@axera-tech.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Shi Zhicheng <shizhicheng@axera-tech.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Linus Walleij <linusw@kernel.org>,
	Drew Fustini <fustini@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, soc@lists.linux.dev
Subject: Re: [PATCH 1/6] dt-bindings: vendor-prefixes: add Axera
Date: Fri, 21 Aug 2026 11:43:55 +0200	[thread overview]
Message-ID: <f7238047-e434-4e46-9f27-183bd94e77c5@kernel.org> (raw)
In-Reply-To: <20260821-ax650-v1-v1-1-e1b013938e6b@axera-tech.com>

On 21/08/2026 11:30, Leng Honglin wrote:
> Add the Axera Semiconductor vendor prefix for devicetree bindings.
> 
> Reviewed-by: Shi Zhicheng <shizhicheng@axera-tech.com>

Where did it happen and what was here exactly reviewed? Did reviewer
understand statement of oversight? I am asking because this is v1 and
has already clearly visible issue (below).


> Signed-off-by: Leng Honglin <lenghonglin@axera-tech.com>
> ---
>  Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> index 396044f368e7..1dbafe682724 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> @@ -219,6 +219,8 @@ patternProperties:
>      description: Shanghai Awinic Technology Co., Ltd.
>    "^axentia,.*":
>      description: Axentia Technologies AB
> +  "^axera,.*":

So your domain is axera.com?


> +    description: Axera Semiconductor Co., Ltd.
Best regards,
Krzysztof

  reply	other threads:[~2026-08-21  9:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-21  9:30 [PATCH 0/6] arm64: Introduce Axera AX650 SoC and AX650 Demo board Leng Honglin
2026-08-21  9:30 ` [PATCH 1/6] dt-bindings: vendor-prefixes: add Axera Leng Honglin
2026-08-21  9:43   ` Krzysztof Kozlowski [this message]
2026-08-21  9:30 ` [PATCH 2/6] dt-bindings: arm: add Axera AX650 SoC and AX650 Demo board Leng Honglin
2026-08-21  9:30 ` [PATCH 3/6] arm64: Kconfig.platforms: add ARCH_AXERA Leng Honglin
2026-08-21  9:30 ` [PATCH 4/6] arm64: defconfig: enable ARCH_AXERA Leng Honglin
2026-08-21  9:30 ` [PATCH 5/6] arm64: dts: axera: add AX650 Demo initial support Leng Honglin
2026-08-21  9:45   ` Krzysztof Kozlowski
2026-08-21 10:02   ` sashiko-bot
2026-08-21  9:30 ` [PATCH 6/6] MAINTAINERS: add Axera ARM SoC support Leng Honglin

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=f7238047-e434-4e46-9f27-183bd94e77c5@kernel.org \
    --to=krzk@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=fustini@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lenghonglin@axera-tech.com \
    --cc=linusw@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=shizhicheng@axera-tech.com \
    --cc=soc@lists.linux.dev \
    --cc=will@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