From: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Bill Richardson <wfrichar@chromium.org>,
Gwendal Grignou <gwendal@chromium.org>
Subject: Re: [PATCH] platform/chrome: add missing include in cros_ec_lpc driver
Date: Mon, 02 Mar 2015 11:21:28 +0100 [thread overview]
Message-ID: <54F439A8.2010606@collabora.co.uk> (raw)
In-Reply-To: <6172990.aK27bmg5kF@wuerfel>
Hello Arnd,
On 03/02/2015 11:01 AM, Arnd Bergmann wrote:
> The newly added cros_ec_lpc driver is meant for x86 but can
> also be built on other architectures. However, the original
> version causes a compile error when built on ARM because
> of a missing #include:
>
> drivers/platform/chrome/cros_ec_lpc.c: In function 'ec_response_timed_out':
> drivers/platform/chrome/cros_ec_lpc.c:40:3: error: implicit declaration of function 'inb' [-Werror=implicit-function-declaration]
> if (!(inb(EC_LPC_ADDR_HOST_CMD) & EC_LPC_STATUS_BUSY_MASK))
> ^
>
> This includes linux/io.h to make it compile reliably.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Fixes: ec2f33ab582bf ("platform/chrome: Add cros_ec_lpc driver for x86 devices")
> Cc: Bill Richardson <wfrichar@chromium.org>
> Cc: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
> Cc: Gwendal Grignou <gwendal@chromium.org>
> Cc: Olof Johansson <olof@lixom.net>
>
> diff --git a/drivers/platform/chrome/cros_ec_lpc.c b/drivers/platform/chrome/cros_ec_lpc.c
> index 822fdb36ded9..f00bf4d246a1 100644
> --- a/drivers/platform/chrome/cros_ec_lpc.c
> +++ b/drivers/platform/chrome/cros_ec_lpc.c
> @@ -23,6 +23,7 @@
>
> #include <linux/dmi.h>
> #include <linux/delay.h>
> +#include <linux/io.h>
> #include <linux/mfd/cros_ec.h>
> #include <linux/mfd/cros_ec_commands.h>
> #include <linux/module.h>
>
I posted the exact same patch [0] on Friday along with other two fixes [1].
Besides this build error fix, in the series there is another patch to make
the driver depends on X86 || COMPILE_TEST which I believe is the best trade
off to avoid building it unnecesarily on ARM but still get build coverage.
Best regards,
Javier
[0]: https://lkml.org/lkml/2015/2/27/9
[1]: https://lkml.org/lkml/2015/2/27/10
prev parent reply other threads:[~2015-03-02 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 10:01 Arnd Bergmann
2015-03-02 10:21 ` Javier Martinez Canillas [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=54F439A8.2010606@collabora.co.uk \
--to=javier.martinez@collabora.co.uk \
--cc=arnd@arndb.de \
--cc=gwendal@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=wfrichar@chromium.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
Powered by JetHome