public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: LeoLiu-oc <LeoLiu-oc@zhaoxin.com>
Cc: rafael@kernel.org, lenb@kernel.org, james.morse@arm.com,
	tony.luck@intel.com, bp@alien8.de, bhelgaas@google.com,
	robert.moore@intel.com, yazen.ghannam@amd.com,
	avadhut.naik@amd.com, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
	acpica-devel@lists.linux.dev, CobeChen@zhaoxin.com,
	TonyWWang@zhaoxin.com, ErosZhang@zhaoxin.com, leoliu@zhaoxin.com
Subject: Re: [PATCH v5 1/4] ACPI: APEI: Move apei_hest_parse() to apei.h
Date: Wed, 5 Mar 2025 17:34:03 -0600	[thread overview]
Message-ID: <20250305233403.GA322933@bhelgaas> (raw)
In-Reply-To: <20250226121838.364533-2-LeoLiu-oc@zhaoxin.com>

On Wed, Feb 26, 2025 at 08:18:35PM +0800, LeoLiu-oc wrote:
> From: LeoLiuoc <LeoLiu-oc@zhaoxin.com>
> 
> Remove static from apei_hest_parse() so that it can be called in another
> file.

> +++ b/drivers/acpi/apei/hest.c
> @@ -134,7 +134,7 @@ static bool is_ghes_assist_struct(struct acpi_hest_header *hest_hdr)
>  
>  typedef int (*apei_hest_func_t)(struct acpi_hest_header *hest_hdr, void *data);
>  
> -static int apei_hest_parse(apei_hest_func_t func, void *data)
> +int apei_hest_parse(apei_hest_func_t func, void *data)
>  {
>  	struct acpi_hest_header *hest_hdr;
>  	int i, rc, len;
> diff --git a/include/acpi/apei.h b/include/acpi/apei.h
> index dc60f7db5524..b79976daa4bb 100644
> --- a/include/acpi/apei.h
> +++ b/include/acpi/apei.h
> @@ -33,6 +33,8 @@ void __init acpi_ghes_init(void);
>  static inline void acpi_ghes_init(void) { }
>  #endif
>  
> +int apei_hest_parse(apei_hest_func_t func, void *data);

Series doesn't build after this patch because we lack the
apei_hest_func_t typedef:

  $ make drivers/acpi/apei/
    CC      drivers/acpi/apei/apei-base.o
  In file included from drivers/acpi/apei/apei-base.c:30:
  ./include/acpi/apei.h:36:21: error: unknown type name ‘apei_hest_func_t’
     36 | int apei_hest_parse(apei_hest_func_t func, void *data);
	|                     ^~~~~~~~~~~~~~~~

The kernel must build and function correctly after each and every
patch in the series.

  reply	other threads:[~2025-03-05 23:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-26 12:18 [PATCH v5 0/4] Parse the HEST PCIe AER and set to relevant registers LeoLiu-oc
2025-02-26 12:18 ` [PATCH v5 1/4] ACPI: APEI: Move apei_hest_parse() to apei.h LeoLiu-oc
2025-03-05 23:34   ` Bjorn Helgaas [this message]
2025-02-26 12:18 ` [PATCH v5 2/4] ACPI: APEI: Add new hest_parse_pcie_aer() LeoLiu-oc
2025-02-26 12:18 ` [PATCH v5 3/4] PCI: Add AER bits #defines for PCIe to PCI/PCI-X Bridge LeoLiu-oc
2025-02-26 12:18 ` [PATCH v5 4/4] PCI: ACPI: Add new pci_acpi_program_hest_aer_params() LeoLiu-oc

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=20250305233403.GA322933@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=CobeChen@zhaoxin.com \
    --cc=ErosZhang@zhaoxin.com \
    --cc=LeoLiu-oc@zhaoxin.com \
    --cc=TonyWWang@zhaoxin.com \
    --cc=acpica-devel@lists.linux.dev \
    --cc=avadhut.naik@amd.com \
    --cc=bhelgaas@google.com \
    --cc=bp@alien8.de \
    --cc=james.morse@arm.com \
    --cc=lenb@kernel.org \
    --cc=leoliu@zhaoxin.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=robert.moore@intel.com \
    --cc=tony.luck@intel.com \
    --cc=yazen.ghannam@amd.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