From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Daniel J Blueman <daniel-JCXMqzvhRcvYtjvyW6yDsg@public.gmane.org>
Cc: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>,
Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] Fix Intel PIIX4 I2C driver build failure
Date: Fri, 5 Oct 2012 09:28:57 +0200 [thread overview]
Message-ID: <20121005092857.3403af0c@endymion.delvare> (raw)
In-Reply-To: <1349410871-17140-1-git-send-email-daniel-JCXMqzvhRcvYtjvyW6yDsg@public.gmane.org>
On Fri, 5 Oct 2012 12:21:11 +0800, Daniel J Blueman wrote:
> Fix build failure in Intel PIIX4 I2C driver.
>
> Signed-off-by: Daniel J Blueman <daniel-JCXMqzvhRcvYtjvyW6yDsg@public.gmane.org>
> ---
> drivers/i2c/busses/i2c-piix4.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/i2c/busses/i2c-piix4.c b/drivers/i2c/busses/i2c-piix4.c
> index ef511df..8bbd6ec 100644
> --- a/drivers/i2c/busses/i2c-piix4.c
> +++ b/drivers/i2c/busses/i2c-piix4.c
> @@ -37,6 +37,7 @@
> #include <linux/stddef.h>
> #include <linux/ioport.h>
> #include <linux/i2c.h>
> +#include <linux/slab.h>
> #include <linux/init.h>
> #include <linux/dmi.h>
> #include <linux/acpi.h>
Good catch. Applied, thanks.
--
Jean Delvare
prev parent reply other threads:[~2012-10-05 7:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 4:21 [PATCH] Fix Intel PIIX4 I2C driver build failure Daniel J Blueman
[not found] ` <1349410871-17140-1-git-send-email-daniel-JCXMqzvhRcvYtjvyW6yDsg@public.gmane.org>
2012-10-05 7:28 ` Jean Delvare [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=20121005092857.3403af0c@endymion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=daniel-JCXMqzvhRcvYtjvyW6yDsg@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.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