public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: "Christophe Leroy" <christophe.leroy@csgroup.eu>,
	"Pali Rohár" <pali@kernel.org>
Cc: Nicholas Piggin <npiggin@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v4 00/17] powerpc/85xx: p2020: Create one unified machine description
Date: Thu, 23 Feb 2023 19:58:11 +1100	[thread overview]
Message-ID: <874jrcbvx8.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <ad8e4adc-2efb-d93e-1221-3a829b454edf@csgroup.eu>

Christophe Leroy <christophe.leroy@csgroup.eu> writes:
> Le 22/02/2023 à 19:22, Pali Rohár a écrit :
>> On Wednesday 22 February 2023 15:42:47 Christophe Leroy wrote:
>>> This patch series unifies all P2020 boards and machine descriptions into
>>> one generic unified P2020 machine description. With this generic machine
>>> description, kernel can boot on any P2020-based board with correct DTS
>>> file.
>>>
>>> Tested on CZ.NIC Turris 1.1 board with has Freescale P2020 processor.
>>> Kernel during booting correctly detects P2020 and prints:
>>> [    0.000000] Using Freescale P2020 machine description
>>>
>>> Changes in v4:
>>> * Added several preparatory cleanup patchs
>>> * Minimised churn by not duplicating helpers at the first place
>>> * Split main patch in two
>>> * Dropped patchs 1 and 2
>>> * Untested beyond basic build test
>> 
>> Changes looks good. I'm happy with them. You can add my:
>> 
>> Reviewed-by: Pali Rohár <pali@kernel.org>
>
> Thanks.
>
> However this series doesn't have the shape for getting merged yet, I've 
> been very quick with the additional patches descriptions and I have not 
> revisited the descriptions of pre-existing patches.
>
> I was expecting you to take over. By the way there's no hurry I guess, 
> we are already in the middle of the merge window, Michael usually 
> doesn't take any more non-fixes patches once the merge window is open, 
> so that series will go in 6.4

Correct.

I'll open next for new patches around 6.3-rc2, so in ~2.5 weeks from now.

cheers

      reply	other threads:[~2023-02-23  8:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22 14:42 [PATCH v4 00/17] powerpc/85xx: p2020: Create one unified machine description Christophe Leroy
2023-02-22 14:42 ` [PATCH v4 01/17] powerpc/fsl_uli1575: Misc cleanup Christophe Leroy
2023-02-22 14:42 ` [PATCH v4 02/17] powerpc/85xx: Rename setup_arch and pic_init on p1023 Christophe Leroy
2023-02-22 14:42 ` [PATCH v4 03/17] powerpc/85xx: Remove DBG() macro Christophe Leroy
2023-02-22 14:42 ` [PATCH v4 04/17] powerpc/85xx: Remove #ifdefs CONFIG_PCI in mpc85xx_ds Christophe Leroy
2023-02-22 14:42 ` [PATCH v4 05/17] powerpc/85xx: mpc85xx_{ds/rdb} compact the call to mpic_alloc() Christophe Leroy
2023-02-22 14:42 ` [PATCH v4 06/17] powerpc/85xx: mpc85xx_{ds/rdb} replace BUG_ON() by WARN_ON() Christophe Leroy
2023-02-22 14:42 ` [PATCH v4 07/17] powerpc/85xx: mpc85xx_{ds/rdb} replace prink by pr_xxx macro Christophe Leroy
2023-02-22 14:42 ` [PATCH v4 08/17] powerpc/85xx: Remove #ifdefs CONFIG_PPC_I8259 in mpc85xx_ds Christophe Leroy
2023-02-22 14:42 ` [PATCH v4 09/17] powerpc/85xx: Remove #ifdef CONFIG_QUICC_ENGINE in mpc85xx_rdb Christophe Leroy
2023-02-22 14:42 ` [PATCH v4 10/17] powerpc/85xx: p2020: Move all P2020 DS machine descriptions to p2020.c Christophe Leroy
2023-02-22 14:42 ` [PATCH v4 11/17] powerpc/85xx: p2020: Move all P2020 RDB " Christophe Leroy
2023-02-22 14:42 ` [PATCH v4 12/17] powerpc/85xx: p2020: Move i8259 code into own function Christophe Leroy
2023-02-22 14:43 ` [PATCH v4 13/17] powerpc/85xx: mpc85xx_ds: Move PCI code into own file Christophe Leroy
2023-02-22 14:43 ` [PATCH v4 14/17] powerpc/85xx: p2020: Unify .setup_arch and .init_IRQ callbacks Christophe Leroy
2023-02-22 14:43 ` [PATCH v4 15/17] powerpc/85xx: p2020: Define just one machine description Christophe Leroy
2023-02-22 14:43 ` [PATCH v4 16/17] powerpc/85xx: p2020: Enable boards by new config option CONFIG_PPC_P2020 Christophe Leroy
2023-02-22 14:43 ` [PATCH v4 17/17] powerpc: dts: turris1x.dts: Remove "fsl,P2020RDB-PC" compatible string Christophe Leroy
2023-02-22 18:22 ` [PATCH v4 00/17] powerpc/85xx: p2020: Create one unified machine description Pali Rohár
2023-02-23  8:37   ` Christophe Leroy
2023-02-23  8:58     ` Michael Ellerman [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=874jrcbvx8.fsf@mpe.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=christophe.leroy@csgroup.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=npiggin@gmail.com \
    --cc=pali@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