From: Thomas Renninger <trenn@suse.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [tip:x86/acpi 2/6] arch/x86/kernel/setup.c:944:2: error: implicit declaration of function 'acpi_
Date: Fri, 28 Sep 2012 16:08:11 +0000 [thread overview]
Message-ID: <201209281808.11405.trenn@suse.de> (raw)
In-Reply-To: <20120928024651.GH9155@localhost>
Hi,
On Friday, September 28, 2012 07:42:49 AM H. Peter Anvin wrote:
> Thank you, Fengguang!
Yes, thanks!
>
> Obviously, we will not push this version of this branch.
I obviously should have done this before:
I now removed the old version, I already had added to our
SUSE head branch and added this one.
This should trigger various .config compile options on different
architectures and when builds succeed, I will again post
(privately to hpa again) the patchset.
The bug was to put an empty declaration of:
static inline void arch_reserve_mem_area(acpi_physical_address addr,
size_t size)
{
}
only into !CONFIG_X86 && CONFIG_ACPI defined area.
Result was that kernel did not build on X86 with ACPI not defined.
Another minor change I am going to add is to name the newly
introduced Kconfig option (bool "..."):
config ACPI_INITRD_TABLE_OVERRIDE
bool "ACPI tables can be passed via uncompressed cpio in initrd"
Question:
Is there a way to get these test builds enabled on a git tree
hosted on git.kernel.org?
I now have an account and if there is some kind of such functionality
I would like to try this out...
Or maybe there is some toolkit so that I can clone my git tree locally
and initiate these test builds here locally?
That would make it easier to pre-test patches in various .configs before
submitting.
Thanks,
Thomas
prev parent reply other threads:[~2012-09-28 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 2:46 [tip:x86/acpi 2/6] arch/x86/kernel/setup.c:944:2: error: implicit declaration of function 'acpi_init Fengguang Wu
2012-09-28 5:42 ` [tip:x86/acpi 2/6] arch/x86/kernel/setup.c:944:2: error: implicit declaration of function 'acpi_ H. Peter Anvin
2012-09-28 16:08 ` Thomas Renninger [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=201209281808.11405.trenn@suse.de \
--to=trenn@suse.de \
--cc=kernel-janitors@vger.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