From: andriy.shevchenko@linux.intel.com (Andy Shevchenko)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1] ARM: pxa/raumfeld: use PROPERTY_ENTRY_U32() directly
Date: Mon, 29 Jan 2018 17:01:54 +0200 [thread overview]
Message-ID: <1517238114.7000.1299.camel@linux.intel.com> (raw)
In-Reply-To: <20180122125529.6291-1-andriy.shevchenko@linux.intel.com>
On Mon, 2018-01-22 at 14:55 +0200, Andy Shevchenko wrote:
> Instead of using PROPERTY_ENTRY_INTEGER() with explicitly supplied
> type,
> use PROPERTY_ENTRY_U32() dedicated macro.
>
> It will help modify internals of built-in device properties API.
>
> No functional change intended.
>
Can someone apply that, or at least Ack? It's needed as a prerequisite
to fix one bug in device property core API.
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> arch/arm/mach-pxa/raumfeld.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm/mach-pxa/raumfeld.c b/arch/arm/mach-
> pxa/raumfeld.c
> index 9d662fed03ec..0bf5419a9d10 100644
> --- a/arch/arm/mach-pxa/raumfeld.c
> +++ b/arch/arm/mach-pxa/raumfeld.c
> @@ -378,9 +378,9 @@ static struct gpiod_lookup_table
> raumfeld_rotary_gpios_table = {
> };
>
> static const struct property_entry raumfeld_rotary_properties[]
> __initconst = {
> - PROPERTY_ENTRY_INTEGER("rotary-encoder,steps-per-period",
> u32, 24),
> - PROPERTY_ENTRY_INTEGER("linux,axis",
> u32, REL_X),
> - PROPERTY_ENTRY_INTEGER("rotary-encoder,relative_axis",
> u32, 1),
> + PROPERTY_ENTRY_U32("rotary-encoder,steps-per-period", 24),
> + PROPERTY_ENTRY_U32("linux,axis", REL_X),
> + PROPERTY_ENTRY_U32("rotary-encoder,relative_axis", 1),
> { },
> };
>
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2018-01-29 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 12:55 [PATCH v1] ARM: pxa/raumfeld: use PROPERTY_ENTRY_U32() directly Andy Shevchenko
2018-01-29 15:01 ` Andy Shevchenko [this message]
2018-01-29 17:31 ` Robert Jarzmik
2018-01-29 17:37 ` Andy Shevchenko
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=1517238114.7000.1299.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.