Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Stefan-gabriel Mirea <stefan-gabriel.mirea@nxp.com>
To:     Greg KH <gregkh@linuxfoundation.org>
CC:     "corbet@lwn.net" <corbet@lwn.net>,
        "robh+dt@kernel.org" <robh+dt@kernel.org>,
        "mark.rutland@arm.com" <mark.rutland@arm.com>,
        "catalin.marinas@arm.com" <catalin.marinas@arm.com>,
        "will@kernel.org" <will@kernel.org>,
        "shawnguo@kernel.org" <shawnguo@kernel.org>,
        Leo Li <leoyang.li@nxp.com>,
        "jslaby@suse.com" <jslaby@suse.com>,
        "linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
        "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
        "linux-arm-kernel@lists.infradead.org" 
        <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v7 0/5] Add initial support for S32V234-EVB
Thread-Topic: [PATCH v7 0/5] Add initial support for S32V234-EVB
Thread-Index: AQHVhEJxhWIy0zctjEGFbT7T+YZTUw==
Date:   Wed, 16 Oct 2019 16:54:58 +0000
Message-ID: <VI1PR0402MB28630943CC0820644D26919CDF920@VI1PR0402MB2863.eurprd04.prod.outlook.com>
References: <1571230107-8493-1-git-send-email-stefan-gabriel.mirea@nxp.com>
 <20191016131728.GA56859@kroah.com>
Accept-Language: en-US
Content-Language: en-US
received-spf: None (protection.outlook.com: nxp.com does not designate
 permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 5444904f-63ba-4061-13fd-08d7525993e4
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Oct 2019 16:54:58.1830
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 686ea1d3-bc2b-4c6f-a92c-d99c5c301635
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: hTlUKMQqrRtiCM1jh8lUsS26CwhIwrfKQDEY5Yf6WcEhfuNZgkHKLTVIhoPQANdUc5ZRFJgWWvJW7dzICxS3Eswglxnw9X+3joHiaL97/Dc=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0402MB3454
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On 10/16/2019 4:17 PM, Greg KH wrote:=0A=
> =0A=
> I've taken patch 3 in my tty-next tree.  The others should probably go=0A=
> through an arm-specific tree, right?=0A=
=0A=
Thank you very much, Greg! That was all for the tty tree.=0A=
=0A=
I think that the other patches should go to the following trees:=0A=
* git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git:=0A=
    patches #1 and possibly #4 (as it covers arch/*/boot/dts/);=0A=
* git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git:=0A=
    patches #2, #5 and possibly #4 (as it covers arch/arm64/boot/dts/)=0A=
* git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git=0A=
    possibly patch #4 (as it covers arch/arm64/boot/dts/freescale/fsl-*)=0A=
=0A=
As a general question, would it be any chance to have the device tree=0A=
included in v5.4 (along with its compatible documentation and config=0A=
definition, without enablement)? That is, only the patches #1, #2 and=0A=
#4, because #3 is a cosmetic change and #5 enables the new configs by=0A=
default. That would complete a minimal support for S32V234-EVB, together=0A=
with the LINFlexD UART driver which was accepted.=0A=
=0A=
From the development process documentation[1]: "An occasional exception=0A=
is made for drivers for previously-unsupported hardware; if they touch=0A=
no in-tree code, they cannot cause regressions and should be safe to add=0A=
at any time".=0A=
=0A=
I know that it mentions only drivers and not device trees, but from the=0A=
history is seems that there have also been dts/dtsi files added outside=0A=
of merge windows, such as:=0A=
* arch/riscv/boot/dts/sifive/fu540-c000.dtsi;=0A=
* arch/riscv/boot/dts/sifive/hifive-unleashed-a00.dts;=0A=
* arch/arm64/boot/dts/arm/vexpress-v2f-1xv7-ca53x2.dts;=0A=
* arch/xtensa/boot/dts/lx200mx.dts;=0A=
* arch/xtensa/boot/dts/kc705.dts;=0A=
* arch/xtensa/boot/dts/xtfpga-flash-128m.dtsi;=0A=
* arch/arm/boot/dts/omap3-beagle-xm-ab.dts;=0A=
* arch/arm/boot/dts/at91-sama5d3_xplained.dts;=0A=
* arch/arm/boot/dts/am335x-boneblack.dts;=0A=
* arch/powerpc/boot/dts/charon.dts.=0A=
=0A=
I am sorry if my question is inopportune, I am definitely not trying to=0A=
rush anyone. I just ask because this has been under review for some=0A=
time and all the feedback has been addressed. We would really appreciate=0A=
to have this SoC and board supported in the following LTS release if=0A=
there are no other issues.=0A=
=0A=
Regards,=0A=
Stefan=0A=
=0A=
[1] https://www.kernel.org/doc/html/v5.3/process/2.Process.html=0A=