mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: 冷红林 <lenghonglin@axera-tech.com>
To: "Krzysztof Kozlowski" <krzk@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	时志成 <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" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"soc@lists.linux.dev" <soc@lists.linux.dev>
Subject: Re: [PATCH 1/6] dt-bindings: vendor-prefixes: add Axera
Date: Mon, 24 Aug 2026 08:41:29 +0000	[thread overview]
Message-ID: <45eb9a27392441898b0c6db7a54a3f61@axera-tech.com> (raw)



> -----邮件原件-----
> 发件人: Krzysztof Kozlowski <krzk@kernel.org>
> 发送时间: 2026年8月21日 17:44
> 收件人: 冷红林 <lenghonglin@axera-tech.com>; Rob Herring
> <robh@kernel.org>; Krzysztof Kozlowski <krzk+dt@kernel.org>; Conor Dooley
> <conor+dt@kernel.org>; 时志成 <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>
> 抄送: devicetree@vger.kernel.org; linux-kernel@vger.kernel.org;
> linux-arm-kernel@lists.infradead.org; soc@lists.linux.dev
> 主题: Re: [PATCH 1/6] dt-bindings: vendor-prefixes: add Axera
> 
> 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).
> 
> 

Hi Krzysztof,

Thanks for pointing this out. You are absolutely right to question the
Reviewed-by tags.

As this is my first time submitting a patch series of this size, I
misunderstood the requirements for the Reviewed-by tag and mistakenly
thought an internal review was sufficient. I apologize for the
confusion and will remove the unconfirmed tags in v2.

> > 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?
> 
> 

Our corporate domain is actually axera-tech.com. I now realize the vendor
prefix should reflect the domain name. I will change the prefix to 
"axera-tech,.*" in v2 to comply with the guidelines.

Best regards,
Leng

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

             reply	other threads:[~2026-08-24  8:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24  8:41 冷红林 [this message]
     [not found] <1eab9e7f03338b673c0e544be7eb4e4421-8-26kernel.org@sslemail.net>
     [not found] ` <202608240638.67O6cTY3025061@spam.axera-tech.com>
2026-08-25  6:28   ` 冷红林
  -- strict thread matches above, loose matches on Subject: below --
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

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=45eb9a27392441898b0c6db7a54a3f61@axera-tech.com \
    --to=lenghonglin@axera-tech.com \
    --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=krzk@kernel.org \
    --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

all inboxes | Powered by JetHome®