From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Hans de Goede <hdegoede@redhat.com>
Cc: Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: [PATCH 01/11] software node: Allow node creation without properties
Date: Wed, 3 Apr 2019 19:45:27 +0300 [thread overview]
Message-ID: <20190403164537.24643-2-heikki.krogerus@linux.intel.com> (raw)
In-Reply-To: <20190403164537.24643-1-heikki.krogerus@linux.intel.com>
Software nodes are not forced to have device properties.
Adding check to property_entries_dup() to make it possible
to create software nodes that don't have any properties.
Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
---
drivers/base/swnode.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/base/swnode.c b/drivers/base/swnode.c
index 7fc5a18e02ad..30077454eb68 100644
--- a/drivers/base/swnode.c
+++ b/drivers/base/swnode.c
@@ -383,6 +383,9 @@ property_entries_dup(const struct property_entry *properties)
int i, n = 0;
int ret;
+ if (!properties)
+ return NULL;
+
while (properties[n].name)
n++;
--
2.20.1
next prev parent reply other threads:[~2019-04-03 16:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 16:45 [PATCH 00/11] Software fwnode references Heikki Krogerus
2019-04-03 16:45 ` Heikki Krogerus [this message]
2019-04-03 16:45 ` [PATCH 02/11] software node: Simplify software_node_release() function Heikki Krogerus
2019-04-03 16:45 ` [PATCH 03/11] software node: Add support for references Heikki Krogerus
2019-04-03 16:45 ` [PATCH 04/11] software node: Implement .get_reference_args fwnode operation Heikki Krogerus
2019-04-03 16:45 ` [PATCH 05/11] ACPI / property: Don't limit named child node matching to data nodes Heikki Krogerus
2019-04-03 16:45 ` [PATCH 06/11] device connection: Find connections also by checking the references Heikki Krogerus
2019-04-03 16:45 ` [PATCH 07/11] usb: typec: Registering real device entries for the muxes Heikki Krogerus
2019-04-03 16:45 ` [PATCH 08/11] platform/x86: intel_cht_int33fe: Provide software nodes for the devices Heikki Krogerus
2019-04-08 16:09 ` Andy Shevchenko
2019-04-08 16:09 ` Andy Shevchenko
2019-04-09 12:41 ` Heikki Krogerus
2019-04-09 12:41 ` Heikki Krogerus
2019-04-03 16:45 ` [PATCH 09/11] platform/x86: intel_cht_int33fe: Provide fwnode for the USB connector Heikki Krogerus
2019-04-08 16:10 ` Andy Shevchenko
2019-04-08 16:10 ` Andy Shevchenko
2019-04-03 16:45 ` [PATCH 10/11] platform/x86: intel_cht_int33fe: Link with external dependencies using fwnodes Heikki Krogerus
2019-04-08 16:42 ` Andy Shevchenko
2019-04-08 16:42 ` Andy Shevchenko
2019-04-09 12:38 ` Heikki Krogerus
2019-04-09 12:38 ` Heikki Krogerus
2019-04-03 16:45 ` [PATCH 11/11] platform/x86: intel_cht_int33fe: Replacing the old connections with references Heikki Krogerus
2019-04-08 16:45 ` Andy Shevchenko
2019-04-08 16:45 ` Andy Shevchenko
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=20190403164537.24643-2-heikki.krogerus@linux.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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