From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-acpi@vger.kernel.org, devicetree@vger.kernel.org,
rafael@kernel.org
Cc: sudeep.holla@arm.com, lorenzo.pieralisi@arm.com,
mika.westerberg@linux.intel.com, mark.rutland@arm.com,
broonie@kernel.org, robh@kernel.org, ahs3@redhat.com
Subject: [PATCH v2 0/3] Fwnode property API fixes for OF, pset and ACPI
Date: Tue, 28 Mar 2017 15:22:16 +0300 [thread overview]
Message-ID: <1490703739-28270-1-git-send-email-sakari.ailus@linux.intel.com> (raw)
Hi folks,
Here are three patches that fix a few issues in the fwnode property API
implementation. They were formerly a part of a larger patchset "Move
firmware specific code to firmware specific locations" here:
<URL:http://www.spinics.net/lists/linux-acpi/msg72174.html>
The v1 (previous version) of the set is also available here:
<URL:http://www.spinics.net/lists/linux-acpi/msg72327.html>
These patches apply cleanly on v4.11-rc1 and linux-next with or without
the ACPI graph support patchset I've sent a moment ago.
changes since v1.1:
- Move fixes to fwnode_property_read_string_array() return value fixes to
respective implementations of those functions, rather than working
around them in the fwnode property interface functions.
- fwnode_property_read_string_array() now may return fewer strings than
requested also on ACPI in order to make behaviour of
fwnode_property_read_string_array() fully consistent.
changes since v1:
- Make prop const. pset_prop_get() returns const struct property_entry *
now in __fwnode_property_read_string_array().
- Make fwnode_property_read_string_array() behave as
of_property_read_string_array() does in terms of the return value.
Sakari Ailus (3):
device property: fwnode_property_read_string_array() may return
-EILSEQ
device property: Fix reading pset strings using array access functions
device property: fwnode_property_read_string_array() returns nr of
strings
drivers/acpi/property.c | 22 +++++++++++++++++-----
drivers/base/property.c | 46 ++++++++++++++++++++++++++++++++--------------
2 files changed, 49 insertions(+), 19 deletions(-)
--
Kind regards,
Sakari
next reply other threads:[~2017-03-28 12:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 12:22 Sakari Ailus [this message]
2017-03-28 12:22 ` [PATCH v2 1/3] device property: fwnode_property_read_string_array() may return -EILSEQ Sakari Ailus
2017-03-28 12:22 ` [PATCH v2 2/3] device property: Fix reading pset strings using array access functions Sakari Ailus
2017-03-28 12:48 ` Mika Westerberg
[not found] ` <1490703739-28270-1-git-send-email-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-03-28 12:22 ` [PATCH v2 3/3] device property: fwnode_property_read_string_array() returns nr of strings Sakari Ailus
[not found] ` <1490703739-28270-4-git-send-email-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-03-28 12:52 ` Mika Westerberg
[not found] ` <20170328125231.GP2957-3PARRvDOhMZrdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2017-03-28 13:07 ` Sakari Ailus
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=1490703739-28270-1-git-send-email-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=ahs3@redhat.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=sudeep.holla@arm.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;
as well as URLs for NNTP newsgroup(s).