From: Ingo Molnar <mingo@kernel.org>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Juergen Gross <jgross@suse.com>,
kbuild-all@01.org, linux-kernel@vger.kernel.org,
tipbuild@zytor.com, Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: Re: [RFC PATCH tip] x86/acpi: u64_x86_init_noop() can be static
Date: Wed, 21 Feb 2018 09:51:48 +0100 [thread overview]
Message-ID: <20180221085148.rs3t7zad73wbpktm@gmail.com> (raw)
In-Reply-To: <20180220123819.GA20499@lkp-wsm-ep1>
* kbuild test robot <fengguang.wu@intel.com> wrote:
>
> Fixes: 62d8b7fba8d3 ("x86/acpi: Add a new x86_init_acpi structure to x86_init_ops")
> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
> ---
> 0 files changed
-ENOPATCH?
Thanks,
Ingo
next prev parent reply other threads:[~2018-02-21 8:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 12:38 [tip:x86/boot 8/9] arch/x86/kernel/x86_init.c:33:5: sparse: symbol 'u64_x86_init_noop' was not declared. Should it be static? kbuild test robot
2018-02-20 12:38 ` [RFC PATCH tip] x86/acpi: u64_x86_init_noop() can be static kbuild test robot
2018-02-21 8:51 ` Ingo Molnar [this message]
2018-02-21 9:16 ` Juergen Gross
2018-02-21 10:20 ` Ingo Molnar
2018-02-22 2:11 ` Fengguang Wu
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=20180221085148.rs3t7zad73wbpktm@gmail.com \
--to=mingo@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=jgross@suse.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tipbuild@zytor.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;
as well as URLs for NNTP newsgroup(s).