From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-acpi@vger.kernel.org
Cc: devicetree@vger.kernel.org, sudeep.holla@arm.com,
lorenzo.pieralisi@arm.com, mika.westerberg@linux.intel.com,
rafael@kernel.org, mark.rutland@arm.com, broonie@kernel.org,
robh@kernel.org, ahs3@redhat.com, frowand.list@gmail.com
Subject: [PATCH 0/7] Constify property fwnode arguments
Date: Mon, 22 May 2017 12:07:35 +0300 [thread overview]
Message-ID: <1495444062-23867-1-git-send-email-sakari.ailus@linux.intel.com> (raw)
Hello everyone,
This set constifies the fwnode arguments in the fwnode property API more
or less the way they are const in OF property API.
Comments are welcome.
The set depends on these patchsets:
<URL:http://www.spinics.net/lists/devicetree/msg177549.html>
<URL:http://www.spinics.net/lists/linux-media/msg114283.html>
<URL:http://marc.info/?l=linux-acpi&m=149544328528001&w=2>
The patches and their dependencies may be also found here:
<URL:https://git.linuxtv.org/sailus/media_tree.git/log/?h=fwnode-const>
(It's uploading right now, so you may need to wait a bit until it's all
up to date.)
Sakari Ailus (7):
ACPI: Constify acpi_get_next_subnode() fwnode argument
ACPI: Constify acpi_bus helper functions, switch to macros
ACPI: Constify internal fwnode arguments
device property: Constify argument to pset fwnode backend
device property: Constify fwnode property API
v4l: fwnode: Constify fwnode endpoints
v4l2-async: Make fwnode const
drivers/acpi/property.c | 90 +++++++++++++++++++---------------
drivers/base/property.c | 91 +++++++++++++++++++----------------
drivers/media/v4l2-core/v4l2-fwnode.c | 12 ++---
drivers/of/property.c | 29 +++++------
include/acpi/acpi_bus.h | 39 +++++++++------
include/linux/acpi.h | 60 ++++++++++++-----------
include/linux/fwnode.h | 25 +++++-----
include/linux/property.h | 58 +++++++++++-----------
include/media/v4l2-async.h | 2 +-
include/media/v4l2-fwnode.h | 6 +--
10 files changed, 226 insertions(+), 186 deletions(-)
--
2.7.4
next reply other threads:[~2017-05-22 9:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 9:07 Sakari Ailus [this message]
2017-05-22 9:07 ` [PATCH 1/7] ACPI: Constify acpi_get_next_subnode() fwnode argument Sakari Ailus
2017-05-22 9:07 ` [PATCH 2/7] ACPI: Constify acpi_bus helper functions, switch to macros Sakari Ailus
2017-05-22 9:07 ` [PATCH 3/7] ACPI: Constify internal fwnode arguments Sakari Ailus
2017-05-22 9:07 ` [PATCH 4/7] device property: Constify argument to pset fwnode backend Sakari Ailus
2017-05-22 9:07 ` [PATCH 5/7] device property: Constify fwnode property API Sakari Ailus
2017-05-22 9:07 ` [PATCH 6/7] v4l: fwnode: Constify fwnode endpoints Sakari Ailus
[not found] ` <1495444062-23867-1-git-send-email-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-05-22 9:07 ` [PATCH 7/7] v4l2-async: Make fwnode const 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=1495444062-23867-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=frowand.list@gmail.com \
--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).