public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chao Fan <fanc.fnst@cn.fujitsu.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: <kbuild-all@01.org>, <tglx@linutronix.de>, <mingo@redhat.com>,
	<hpa@zytor.com>, <x86@kernel.org>, <linux-kernel@vger.kernel.org>,
	<keescook@chromium.org>, <bhe@redhat.com>,
	<indou.takao@jp.fujitsu.com>, <caoj.fnst@cn.fujitsu.com>,
	<douly.fnst@cn.fujitsu.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Len Brown <lenb@kernel.org>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	<linux-efi@vger.kernel.org>, <linux-acpi@vger.kernel.org>
Subject: Re: [RFC PATCH] x86/boot: get_acpi_srat_table() can be static
Date: Tue, 11 Sep 2018 16:55:25 +0800	[thread overview]
Message-ID: <20180911085525.GF8519@localhost.localdomain> (raw)
In-Reply-To: <20180911085226.GA25670@athens>

On Tue, Sep 11, 2018 at 04:52:26PM +0800, kbuild test robot wrote:
>
>Fixes: cc1a4e2a5474 ("x86/boot: Add acpitb.c to parse acpi tables")
>Signed-off-by: kbuild test robot <fengguang.wu@intel.com>
>---
> acpitb.c |    2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/arch/x86/boot/compressed/acpitb.c b/arch/x86/boot/compressed/acpitb.c
>index 66c5154..4ddd732 100644
>--- a/arch/x86/boot/compressed/acpitb.c
>+++ b/arch/x86/boot/compressed/acpitb.c
>@@ -279,7 +279,7 @@ static acpi_physical_address get_rsdp_addr(void)
> 	return pa;
> }
> 
>-struct acpi_table_header *get_acpi_srat_table(void)
>+static struct acpi_table_header *get_acpi_srat_table(void)

Good catch, will add it.

Thanks,
Chao Fan

> {
> 	char *args = (char *)get_cmd_line_ptr();
> 	acpi_physical_address acpi_table;
>
>



  reply	other threads:[~2018-09-11  8:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-10 12:40 [PATCH v6 0/3] x86/boot/KASLR: Parse ACPI table and limit kaslr in immovable memory Chao Fan
2018-09-10 12:40 ` [PATCH v6 1/3] x86/boot: Add acpitb.c to parse acpi tables Chao Fan
2018-09-10 20:13   ` Rafael J. Wysocki
2018-09-11  1:27     ` Chao Fan
2018-09-11  7:41       ` Rafael J. Wysocki
2018-09-11  7:52         ` Chao Fan
2018-09-11  8:52   ` [RFC PATCH] x86/boot: get_acpi_srat_table() can be static kbuild test robot
2018-09-11  8:55     ` Chao Fan [this message]
2018-09-11  8:52   ` [PATCH v6 1/3] x86/boot: Add acpitb.c to parse acpi tables kbuild test robot
2018-09-12  7:08   ` kbuild test robot
2018-09-10 12:40 ` [PATCH v6 2/3] x86/boot/KASLR: Walk srat tables to filter immovable memory Chao Fan
2018-09-10 12:40 ` [PATCH v6 3/3] x86/boot/KASLR: Limit kaslr to choosing the " Chao Fan
2018-09-11  1:13 ` [PATCH v6 0/3] x86/boot/KASLR: Parse ACPI table and limit kaslr in " Chao Fan
2018-09-11  7:28   ` Rafael J. Wysocki
2018-09-11  7:53     ` Chao Fan

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=20180911085525.GF8519@localhost.localdomain \
    --to=fanc.fnst@cn.fujitsu.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=bhe@redhat.com \
    --cc=caoj.fnst@cn.fujitsu.com \
    --cc=douly.fnst@cn.fujitsu.com \
    --cc=fengguang.wu@intel.com \
    --cc=hpa@zytor.com \
    --cc=indou.takao@jp.fujitsu.com \
    --cc=kbuild-all@01.org \
    --cc=keescook@chromium.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rjw@rjwysocki.net \
    --cc=tglx@linutronix.de \
    --cc=x86@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