Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Tzu-Hao Wei" <twei@axiado.com>,
	soc@kernel.org, linux-arm-kernel@lists.infradead.org
Cc: "Mark Brown" <broonie@kernel.org>
Subject: Re: [GIT PULL] Axiado DT updates for v7.4
Date: Thu, 19 Nov 2026 09:57:35 +0100	[thread overview]
Message-ID: <3b494499-c8e4-4670-8d61-b770d2298331@app.fastmail.com> (raw)
In-Reply-To: <2b550966-0185-47bd-80bb-ebab6f717e2c@axiado.com>

On Tue, Nov 10, 2026, at 19:24, Tzu-Hao Wei wrote:
> On 10/29/2026 3:36 AM, Tzu-Hao Wei wrote:
>> 
>> Hi SoC maintainers,
>> 
>> Please pull the following Axiado Devicetree updates for v7.4.
>> 
>> This pull request includes:
>>    Initial Devicetree support for the AX3005 SoC and evaluation board.
>>    AX3005 EVK compatible string in the Axiado board binding.
>>    Minor hexadecimal formatting cleanup in the AX3000 Devicetree.
>
> Just following up on the Axiado DT pull request.
>
> Could you please let me know if there are any concerns with the pull
> request, or if these changes should be deferred to the next merge window?

Sorry for the delay in replying, I just got back to merging content
for the next release.

Your pull request came in at the wrong time for 7.4, we really
need to have everything queued up well in advance of the merge window
to ensure it's properly tested, please see
Documentation/process/maintainer-soc.rst for the usual rules.

As the contents of your pull request look fine, we could either
pull it in for 7.5 now, or you can rebase it on top of v7.4-rc1
and send an updated pull request.

A few more things I noticed:

 - you have signed the pull request, but I can't find your
   signing key on the usual gpg servers. Please upload the
   key you used and let us know about it.

 - The contents you send should be in Linux-next for a while
   before you send a PR. Please email Mark Brown (on Cc here)
   with the details of which branch you want him to include
   in future linux-next builds.

 - As a maintainer, you can apply for a kernel.org account
   and host your trees on git.kernel.org, which we generally
   prefer over github, see
   https://korg.docs.kernel.org/accounts.html for how to
   apply.

      Arnd


      reply	other threads:[~2026-11-19  8:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-28 19:36 [GIT PULL] Axiado DT updates for v7.4 Tzu-Hao Wei
2026-11-10 18:24 ` Tzu-Hao Wei
2026-11-19  8:57   ` Arnd Bergmann [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=3b494499-c8e4-4670-8d61-b770d2298331@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=soc@kernel.org \
    --cc=twei@axiado.com \
    /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