From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
To: John Youn <johnyoun@synopsys.com>
Cc: linux-kernel@vger.kernel.org, Hanjun Guo <hanjun.guo@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Suthikulpanit, Suravee" <Suravee.Suthikulpanit@amd.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>
Subject: Re: [PATCH] include/linux/property.h: fix typo/compile error
Date: Fri, 30 Sep 2016 02:21:03 +0200 [thread overview]
Message-ID: <aa6a6ed6-345f-8505-368f-6447f699493f@intel.com> (raw)
In-Reply-To: <2de3b929290d88a723ed829a3e3cbd02044714df.1475114627.git.johnyoun@synopsys.com>
On 9/29/2016 4:10 AM, John Youn wrote:
> This fixes commit d76eebfa175e ("include/linux/property.h: fix build
> issues with gcc-4.4.4").
>
> With that commit we get the following compile error when using the
> PROPERTY_ENTRY_INTEGER_ARRAY macro.
>
> ../include/linux/property.h:201:39: error: ‘u32_data’ undeclared (first
> use in this function)
> PROPERTY_ENTRY_INTEGER_ARRAY(_name_, u32, _val_)
> ^
> ../include/linux/property.h:193:17: note: in definition of macro
> ‘PROPERTY_ENTRY_INTEGER_ARRAY’
> { .pointer = { _type_##_data = _val_ } }, \
> ^
>
> This needs a '.' to reference the union member. It seems this was just
> overlooked here since it is done correctly in similar constructs in
> other parts of the original commit.
>
> This fix is in preparation of upcoming commits that will use this macro.
>
> Fixes: commit d76eebfa175e ("include/linux/property.h: fix build issues with gcc-4.4.4")
> Signed-off-by: John Youn <johnyoun@synopsys.com>
Applied.
Thanks,
Rafael
> ---
> include/linux/property.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/property.h b/include/linux/property.h
> index 3a2f9ae..856e50b 100644
> --- a/include/linux/property.h
> +++ b/include/linux/property.h
> @@ -190,7 +190,7 @@ struct property_entry {
> .length = ARRAY_SIZE(_val_) * sizeof(_type_), \
> .is_array = true, \
> .is_string = false, \
> - { .pointer = { _type_##_data = _val_ } }, \
> + { .pointer = { ._type_##_data = _val_ } }, \
> }
>
> #define PROPERTY_ENTRY_U8_ARRAY(_name_, _val_) \
prev parent reply other threads:[~2016-09-30 0:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 2:10 John Youn
2016-09-30 0:21 ` Rafael J. Wysocki [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=aa6a6ed6-345f-8505-368f-6447f699493f@intel.com \
--to=rafael.j.wysocki@intel.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=hanjun.guo@linaro.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=johnyoun@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
/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
all inboxes | Powered by JetHome®