From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Linus Walleij <linus.walleij@linaro.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pinctrl: Include <linux/bug.h> to prevent compile errors
Date: Fri, 9 Mar 2012 15:32:07 -0500 [thread overview]
Message-ID: <20120309203207.GB10835@windriver.com> (raw)
In-Reply-To: <1331324305-1649-1-git-send-email-swarren@wwwdotorg.org>
[[PATCH] pinctrl: Include <linux/bug.h> to prevent compile errors] On 09/03/2012 (Fri 13:18) Stephen Warren wrote:
> Macros in <linux/pinctrl/machine.h> call ARRAY_SIZE(), the definition of
> which eventually calls BUILD_BUG_ON_ZERO(), which is defined in
> <linux/bug.h>. Include that so that every .c file using the pinctrl macros
> doesn't have to do that itself.
Which C files are failing? The approach was to be adding it only
for headers with static inlines which use it, and add it to C files
that are actually *deploying* the macros.
Thanks,
Paul.
>
> Signed-off-by: Stephen Warren <swarren@wwwdotorg.org>
> ---
> include/linux/pinctrl/machine.h | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/include/linux/pinctrl/machine.h b/include/linux/pinctrl/machine.h
> index fee4349..012731a 100644
> --- a/include/linux/pinctrl/machine.h
> +++ b/include/linux/pinctrl/machine.h
> @@ -12,7 +12,9 @@
> #ifndef __LINUX_PINCTRL_MACHINE_H
> #define __LINUX_PINCTRL_MACHINE_H
>
> -#include "pinctrl-state.h"
> +#include <linux/bug.h>
> +
> +#include "pinctrl.h"
>
> enum pinctrl_map_type {
> PIN_MAP_TYPE_INVALID,
> --
> 1.7.0.4
>
next prev parent reply other threads:[~2012-03-09 20:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 20:18 [PATCH] pinctrl: Include <linux/bug.h> to prevent compile errors Stephen Warren
2012-03-09 20:32 ` Paul Gortmaker [this message]
2012-03-09 20:43 ` Stephen Warren
2012-03-09 21:29 ` Paul Gortmaker
2012-03-09 23:09 ` Stephen Warren
2012-03-12 19:44 ` Linus Walleij
2012-03-12 20:55 ` Stephen Warren
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=20120309203207.GB10835@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swarren@wwwdotorg.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