From: Ben Hutchings <ben@decadent.org.uk>
To: whiteheadm@acm.org, Ben Hutchings <ben.hutchings@codethink.co.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3.16] x86/eisa: Add missing include
Date: Tue, 29 Jan 2019 18:08:40 +0000 [thread overview]
Message-ID: <20d22d3678062231a459fcf8ae05ee35efc4b425.camel@decadent.org.uk> (raw)
In-Reply-To: <CAP8WD_ZoF+C=R07D6uio1fdDVJD5XLS64g=Cgced7BHZ1GbXUQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]
On Tue, 2019-01-22 at 14:51 +0000, tedheadster wrote:
> Ben, please backport Thomas Gleixner's patch to the 3.16 series.
This was already in my queue for the next update.
Ben.
> commit ef1d4deab953ecb1dfcf9f167043bda8b3f14a11
> Author: Thomas Gleixner <tglx@linutronix.de>
> Date: Thu Aug 31 20:08:16 2017 +0200
>
> x86/eisa: Add missing include
>
> The seperation of the EISA init missed to include linux/io.h which breaks
> the build with some special configurations.
>
> Reported-by: Ingo Molnar <mingo@kernel.org>
> Fixes: f7eaf6e00fd5 ("x86/boot: Move EISA setup to a separate file")
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
>
> diff --git a/arch/x86/kernel/eisa.c b/arch/x86/kernel/eisa.c
> index 881f9236ebff..f260e452e4f8 100644
> --- a/arch/x86/kernel/eisa.c
> +++ b/arch/x86/kernel/eisa.c
> @@ -5,6 +5,7 @@
> */
> #include <linux/ioport.h>
> #include <linux/eisa.h>
> +#include <linux/io.h>
>
> static __init int eisa_bus_probe(void)
> {
>
>
--
Ben Hutchings
The obvious mathematical breakthrough [to break modern encryption]
would be development of an easy way to factor large prime numbers.
- Bill Gates
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-01-29 18:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 14:11 [PATCH 3.16] x86/eisa: Add missing include tedheadster
2019-01-29 18:08 ` Ben Hutchings [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=20d22d3678062231a459fcf8ae05ee35efc4b425.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=ben.hutchings@codethink.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=whiteheadm@acm.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;
as well as URLs for NNTP newsgroup(s).