mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Harshit Shah <hshah@axiado.com>
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Bartosz Golaszewski" <brgl@bgdev.pl>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Catalin Marinas" <catalin.marinas@arm.com>,
	"Will Deacon" <will@kernel.org>, "Jan Kotas" <jank@cadence.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Jiri Slaby" <jirislaby@kernel.org>,
	"Michal Simek" <michal.simek@amd.com>,
	"Przemysław Gaj" <pgaj@cadence.com>,
	"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
	"Frank Li" <Frank.Li@nxp.com>,
	"Boris Brezillon" <bbrezillon@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>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"soc@lists.linux.dev" <soc@lists.linux.dev>,
	"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
	"linux-i3c@lists.infradead.org" <linux-i3c@lists.infradead.org>
Subject: Re: [PATCH v6 00/10] Axiado AX3000 SoC and Evaluation Board Support
Date: Sat, 19 Jul 2025 01:09:32 +0000	[thread overview]
Message-ID: <06f00d05-b8ca-41fa-9e5e-9cee3cfcfae1@axiado.com> (raw)
In-Reply-To: <e461e5ed-f512-4d3b-9903-8092dab7f81d@linaro.org>

On 7/17/2025 11:14 PM, Krzysztof Kozlowski wrote:
>> Hi all,
>>
>> This patch series was reviewed by Krzysztof, and I am wondering if it’s
>> queued for the next merge window. Thanks in advance!
> It's not, unless you received clear notice about it. Please read
> maintainer soc profile how to send patches for merging.

Thank you Krzysztof for the reference.

We went through maintainer-soc.rst 
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/maintainer-soc.rst?h=v6.16-rc1#n73) 


It mentions about the special case where "Introducing a completely new 
SoC platform." we can submit patches to soc@kernel.org directly.

However I see two different points in the doc.

1. Submitting patches directly to soc@kernel.org with email

2. There is also mention about the "Branches and Pull requests"

(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/maintainer-soc.rst?h=v6.16-rc1#n186). 


I think if we need to use this approach then we need to create a new 
branch on soc and create a pull request based on the same. (with the soc 
tree[1])


We are not sure if we should follow which method for this purpose. Can 
you please help on the same? Apologies for too long questions.


[1] https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git/

Regards,

Harshit.


  reply	other threads:[~2025-07-19  1:09 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-03 18:20 Harshit Shah
2025-07-03 18:20 ` [PATCH v6 01/10] dt-bindings: vendor-prefixes: Add Axiado Corporation Harshit Shah
2025-07-03 18:20 ` [PATCH v6 02/10] dt-bindings: arm: axiado: add AX3000 EVK compatible strings Harshit Shah
2025-07-03 18:20 ` [PATCH v6 03/10] dt-bindings: gpio: cdns: convert to YAML Harshit Shah
2025-07-03 18:20 ` [PATCH v6 04/10] dt-bindings: gpio: cdns: add Axiado AX3000 GPIO variant Harshit Shah
2025-07-04  7:02   ` Krzysztof Kozlowski
2025-07-03 18:20 ` [PATCH v6 05/10] dt-bindings: serial: cdns: add Axiado AX3000 UART controller Harshit Shah
2025-07-04  7:02   ` Krzysztof Kozlowski
2025-07-03 18:20 ` [PATCH v6 06/10] dt-bindings: i3c: cdns: add Axiado AX3000 I3C controller Harshit Shah
2025-07-03 18:20 ` [PATCH v6 07/10] arm64: add Axiado SoC family Harshit Shah
2025-07-03 18:20 ` [PATCH v6 08/10] arm64: dts: axiado: Add initial support for AX3000 SoC and eval board Harshit Shah
2025-07-03 18:20 ` [PATCH v6 09/10] arm64: defconfig: enable the Axiado family Harshit Shah
2025-07-03 18:20 ` [PATCH v6 10/10] MAINTAINERS: Add entry for Axiado Harshit Shah
2025-07-17 23:48 ` [PATCH v6 00/10] Axiado AX3000 SoC and Evaluation Board Support Harshit Shah
2025-07-18  6:14   ` Krzysztof Kozlowski
2025-07-19  1:09     ` Harshit Shah [this message]
2025-07-20 12:09       ` Krzysztof Kozlowski
2025-07-21 14:31         ` Arnd Bergmann
2025-07-21 20:43           ` Harshit Shah
2025-07-21 20:54             ` Arnd Bergmann
2025-07-21 21:43               ` Harshit Shah
2025-07-22 20:15 Harshit Shah
2025-07-23  8:25 ` Bartosz Golaszewski
2025-07-23 17:53   ` Harshit Shah

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=06f00d05-b8ca-41fa-9e5e-9cee3cfcfae1@axiado.com \
    --to=hshah@axiado.com \
    --cc=Frank.Li@nxp.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=arnd@arndb.de \
    --cc=bbrezillon@kernel.org \
    --cc=brgl@bgdev.pl \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jank@cadence.com \
    --cc=jirislaby@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-i3c@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=michal.simek@amd.com \
    --cc=pgaj@cadence.com \
    --cc=robh@kernel.org \
    --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®