From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Hans de Goede <hdegoede@redhat.com>,
Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH v5 1/4] device property: allow to constify properties
Date: Fri, 03 Feb 2017 13:40:21 +0200 [thread overview]
Message-ID: <1486122021.2133.371.camel@linux.intel.com> (raw)
In-Reply-To: <20170203014128.317-2-dmitry.torokhov@gmail.com>
On Thu, 2017-02-02 at 17:41 -0800, Dmitry Torokhov wrote:
> There is no reason why statically defined properties should be
> modifiable,
> so let's make device_add_properties() and the rest of pset_*()
> functions to
> take const pointers to properties.
>
> This will allow us to mark properties as const/__initconst at
> definition
> sites.
>
Looks good to me.
FWIW:
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Though, nitpicks below.
> static struct property_set *pset_copy_set(const struct property_set
> *pset)
> {
> - const struct property_entry *entry;
> + struct property_entry *props;
Can we leave the name?
> - p->properties = kcalloc(n + 1, sizeof(*entry), GFP_KERNEL);
>
> + p->properties = props = kcalloc(n + 1, sizeof(*props),
> GFP_KERNEL);
> if (!p->properties) {
> kfree(p);
> return ERR_PTR(-ENOMEM);
> }
>
> for (i = 0; i < n; i++) {
> - int ret = pset_copy_entry(&p->properties[i],
> + int ret = pset_copy_entry(&props[i],
> &pset->properties[i]);
Do we need these changes?
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-02-03 11:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 1:41 [PATCH v5 0/4] Export APIs to copy device properties & more Dmitry Torokhov
2017-02-03 1:41 ` [PATCH v5 1/4] device property: allow to constify properties Dmitry Torokhov
2017-02-03 11:40 ` Andy Shevchenko [this message]
2017-02-03 15:09 ` Dmitry Torokhov
2017-02-03 1:41 ` [PATCH v5 2/4] device property: constify property arrays values Dmitry Torokhov
2017-02-03 11:43 ` Andy Shevchenko
2017-02-03 15:12 ` Dmitry Torokhov
2017-02-03 1:41 ` [PATCH v5 3/4] device property: export code duplicating array of property entries Dmitry Torokhov
2017-02-03 11:45 ` Andy Shevchenko
2017-02-03 15:15 ` Dmitry Torokhov
2017-02-03 1:41 ` [PATCH v5 4/4] i2c: allow specify device properties in i2c_board_info Dmitry Torokhov
2017-02-03 11:46 ` Andy Shevchenko
2017-02-07 12:44 ` Rafael J. Wysocki
2017-02-07 13:25 ` Wolfram Sang
2017-02-09 13:52 ` [PATCH v5 0/4] Export APIs to copy device properties & more 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=1486122021.2133.371.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=wsa@the-dreams.de \
/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).