From: Nathan Lynch <nathanl@linux.ibm.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH v1 1/9] powerpc/machdep: Define 'compatible' property in ppc_md and use it
Date: Wed, 15 Feb 2023 12:44:37 -0600 [thread overview]
Message-ID: <874jrmahuy.fsf@linux.ibm.com> (raw)
In-Reply-To: <04ed69b4226633ab90983d7efb5bd4791078fe71.1676465585.git.christophe.leroy@csgroup.eu>
Christophe Leroy <christophe.leroy@csgroup.eu> writes:
> Most probe functions do nothing else than checking whether
> the machine is compatible to a given string.
>
> Define that string in ppc_md structure and check it directly from
> probe_machine() instead of using ppc_md.probe() for that.
>
> Keep checking in ppc_md.probe() only for more complex probing.
>
> Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
> ---
> v3: New
> ---
> arch/powerpc/include/asm/machdep.h | 1 +
> arch/powerpc/kernel/setup-common.c | 13 +++++++------
> 2 files changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/arch/powerpc/include/asm/machdep.h b/arch/powerpc/include/asm/machdep.h
> index 378b8d5836a7..c5dfe5ff923c 100644
> --- a/arch/powerpc/include/asm/machdep.h
> +++ b/arch/powerpc/include/asm/machdep.h
> @@ -20,6 +20,7 @@ struct pci_host_bridge;
>
> struct machdep_calls {
> char *name;
> + char *compatible;
Seems like 'compatible' ought to be const char *? Possibly 'name' also.
I'm able to build ppc64le with those changes, at least.
WARNING: multiple messages have this Message-ID (diff)
From: Nathan Lynch <nathanl@linux.ibm.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH v1 1/9] powerpc/machdep: Define 'compatible' property in ppc_md and use it
Date: Wed, 15 Feb 2023 12:44:37 -0600 [thread overview]
Message-ID: <874jrmahuy.fsf@linux.ibm.com> (raw)
In-Reply-To: <04ed69b4226633ab90983d7efb5bd4791078fe71.1676465585.git.christophe.leroy@csgroup.eu>
Christophe Leroy <christophe.leroy@csgroup.eu> writes:
> Most probe functions do nothing else than checking whether
> the machine is compatible to a given string.
>
> Define that string in ppc_md structure and check it directly from
> probe_machine() instead of using ppc_md.probe() for that.
>
> Keep checking in ppc_md.probe() only for more complex probing.
>
> Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
> ---
> v3: New
> ---
> arch/powerpc/include/asm/machdep.h | 1 +
> arch/powerpc/kernel/setup-common.c | 13 +++++++------
> 2 files changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/arch/powerpc/include/asm/machdep.h b/arch/powerpc/include/asm/machdep.h
> index 378b8d5836a7..c5dfe5ff923c 100644
> --- a/arch/powerpc/include/asm/machdep.h
> +++ b/arch/powerpc/include/asm/machdep.h
> @@ -20,6 +20,7 @@ struct pci_host_bridge;
>
> struct machdep_calls {
> char *name;
> + char *compatible;
Seems like 'compatible' ought to be const char *? Possibly 'name' also.
I'm able to build ppc64le with those changes, at least.
next prev parent reply other threads:[~2023-02-15 18:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 12:53 [PATCH v1 1/9] powerpc/machdep: Define 'compatible' property in ppc_md and use it Christophe Leroy
2023-02-15 12:53 ` Christophe Leroy
2023-02-15 12:53 ` [PATCH v1 2/9] powerpc/platforms: Use 'compatible' property for simple cases Christophe Leroy
2023-02-15 12:53 ` Christophe Leroy
2023-02-15 12:53 ` [PATCH v1 3/9] powerpc/47x: Split ppc47x machine in two Christophe Leroy
2023-02-15 12:53 ` Christophe Leroy
2023-02-15 21:58 ` Michael Ellerman
2023-02-15 21:58 ` Michael Ellerman
2023-02-15 12:53 ` [PATCH v1 4/9] powerpc/gamecube|wii : Use machine_device_initcall() Christophe Leroy
2023-02-15 12:53 ` Christophe Leroy
2023-02-15 12:53 ` [PATCH v1 5/9] powerpc/85xx: Fix function naming for p1023_rdb platform Christophe Leroy
2023-02-15 12:53 ` Christophe Leroy
2023-02-15 12:53 ` [PATCH v1 6/9] powerpc: Make generic_calibrate_decr() the default Christophe Leroy
2023-02-15 12:53 ` Christophe Leroy
2023-02-15 12:53 ` [PATCH v1 7/9] powerpc: Add ppc_md_progress() Christophe Leroy
2023-02-15 12:53 ` Christophe Leroy
2023-02-15 12:53 ` [PATCH v1 8/9] powerpc: Use ppc_md_progress() Christophe Leroy
2023-02-15 12:53 ` Christophe Leroy
2023-02-15 12:53 ` [PATCH v1 9/9] powerpc/85xx: Don't check ppc_md.progress in mpc85xx_cds_setup_arch() Christophe Leroy
2023-02-15 12:53 ` Christophe Leroy
2023-02-15 18:44 ` Nathan Lynch [this message]
2023-02-15 18:44 ` [PATCH v1 1/9] powerpc/machdep: Define 'compatible' property in ppc_md and use it Nathan Lynch
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=874jrmahuy.fsf@linux.ibm.com \
--to=nathanl@linux.ibm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.