From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: linux-acpi@vger.kernel.org, rafael@kernel.org
Subject: Re: [PATCH v3 6/8] ACPI: property: Unify integer value reading functions
Date: Fri, 27 May 2022 18:12:55 +0300 [thread overview]
Message-ID: <YpDqdzZEPcOhClFY@paasikivi.fi.intel.com> (raw)
In-Reply-To: <Yo5j/N+qoSSYexnj@smile.fi.intel.com>
Hi Andy,
On Wed, May 25, 2022 at 08:14:36PM +0300, Andy Shevchenko wrote:
> On Wed, May 25, 2022 at 04:01:21PM +0300, Sakari Ailus wrote:
> > Unify functions reading ACPI property integer values into a single macro
> > using C99 _Generic().
> >
> > Also use size_t for the counter instead of int.
>
> Thanks for an update!
>
> ...
>
> > +#define acpi_copy_property_array_uint(items, val, nval) \
> > + ({ \
>
> You can define local copies of (read-only) parameters and avoid adding
> parentheses each time you access them.
Sounds good.
>
> > + size_t i; \
> > + int ret = 0; \
> > + \
> > + for (i = 0; i < (nval); i++) { \
> > + if ((items)[i].type != ACPI_TYPE_INTEGER) { \
> > + ret = -EPROTO; \
> > + break; \
> > + } \
> > + if ((items)[i].integer.value > _Generic((val), \
> > + u8: U8_MAX, \
> > + u16: U16_MAX, \
> > + u32: U32_MAX, \
> > + u64: U64_MAX, \
> > + default: 0U)) { \
>
> I think nobody will die if you add one more TAB to each line and make \ be
> consistent column wise.
I think it's unlikely, too. Still the above is consistent with the rest of
recently merged patches adding similar constructs.
--
Kind regards,
Sakari Ailus
next prev parent reply other threads:[~2022-05-27 15:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 13:01 [PATCH v3 0/8] ACPI: Buffer property and reference as string support Sakari Ailus
2022-05-25 13:01 ` [PATCH v3 1/8] ACPI: property: Return type of acpi_add_nondev_subnodes() should be bool Sakari Ailus
2022-05-25 17:15 ` Andy Shevchenko
2022-05-25 13:01 ` [PATCH v3 2/8] ACPI: property: Tie data nodes to acpi handles Sakari Ailus
2022-05-25 17:20 ` Andy Shevchenko
2022-05-27 14:35 ` Sakari Ailus
2022-05-26 19:19 ` Rafael J. Wysocki
2022-05-27 9:02 ` Sakari Ailus
2022-05-27 17:04 ` Rafael J. Wysocki
2022-05-27 20:59 ` Sakari Ailus
2022-05-28 13:56 ` Rafael J. Wysocki
2022-05-25 13:01 ` [PATCH v3 3/8] ACPI: property: Use acpi_object_type consistently in property ref parsing Sakari Ailus
2022-05-25 17:23 ` Andy Shevchenko
2022-05-25 13:01 ` [PATCH v3 4/8] ACPI: property: Move property ref argument parsing into a new function Sakari Ailus
2022-05-25 17:28 ` Andy Shevchenko
2022-05-27 14:37 ` Sakari Ailus
2022-05-25 13:01 ` [PATCH v3 5/8] ACPI: property: Switch node property referencing from ifs to a switch Sakari Ailus
2022-05-25 17:30 ` Andy Shevchenko
2022-05-25 13:01 ` [PATCH v3 6/8] ACPI: property: Unify integer value reading functions Sakari Ailus
2022-05-25 17:14 ` Andy Shevchenko
2022-05-27 15:12 ` Sakari Ailus [this message]
2022-05-25 13:01 ` [PATCH v3 7/8] ACPI: property: Add support for parsing buffer property UUID Sakari Ailus
2022-05-25 17:44 ` Andy Shevchenko
2022-05-27 12:43 ` Sakari Ailus
2022-05-25 13:01 ` [PATCH v3 8/8] ACPI: property: Read buffer properties as integers Sakari Ailus
2022-05-25 17:36 ` Andy Shevchenko
2022-05-27 10:01 ` Sakari Ailus
2022-06-09 18:38 ` [PATCH v3 0/8] ACPI: Buffer property and reference as string support Rafael J. Wysocki
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=YpDqdzZEPcOhClFY@paasikivi.fi.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=rafael@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