From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-input@vger.kernel.org, linux-doc@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v1] Input: docs - use PROPERTY_ENTRY_U32() directly
Date: Mon, 22 Jan 2018 09:28:33 -0800 [thread overview]
Message-ID: <20180122172833.hvfg2qcnpzscbymm@dtor-ws> (raw)
In-Reply-To: <20180122125457.6226-1-andriy.shevchenko@linux.intel.com>
On Mon, Jan 22, 2018 at 02:54:57PM +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.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Applied, thank you.
> ---
> Documentation/input/devices/rotary-encoder.rst | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/input/devices/rotary-encoder.rst b/Documentation/input/devices/rotary-encoder.rst
> index b07b20a295ac..810ae02bdaa0 100644
> --- a/Documentation/input/devices/rotary-encoder.rst
> +++ b/Documentation/input/devices/rotary-encoder.rst
> @@ -108,9 +108,9 @@ example below:
> };
>
> static const struct property_entry rotary_encoder_properties[] __initconst = {
> - PROPERTY_ENTRY_INTEGER("rotary-encoder,steps-per-period", u32, 24),
> - PROPERTY_ENTRY_INTEGER("linux,axis", u32, ABS_X),
> - PROPERTY_ENTRY_INTEGER("rotary-encoder,relative_axis", u32, 0),
> + PROPERTY_ENTRY_U32("rotary-encoder,steps-per-period", 24),
> + PROPERTY_ENTRY_U32("linux,axis", ABS_X),
> + PROPERTY_ENTRY_U32("rotary-encoder,relative_axis", 0),
> { },
> };
>
> --
> 2.15.1
>
--
Dmitry
prev parent reply other threads:[~2018-01-22 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 12:54 [PATCH v1] Input: docs - use PROPERTY_ENTRY_U32() directly Andy Shevchenko
2018-01-22 17:28 ` Dmitry Torokhov [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=20180122172833.hvfg2qcnpzscbymm@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-input@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).