From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rob Herring <robh@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
devicetree@vger.kernel.org
Subject: [PATCH v5 0/3] device property: Add fwnode_get_name() helper
Date: Wed, 28 Nov 2018 14:59:49 +0300 [thread overview]
Message-ID: <20181128115952.80890-1-heikki.krogerus@linux.intel.com> (raw)
Hi,
There are no changes compared to v4. I'm resending because of the
extra patch in v4. Sorry for that. This was the v4 cover letter:
I'm now returning -EOVERFLOW if the buffer is not big enough as
proposed by Andy.
This is the cover letter from v3:
This is the third version of my proposal for this helper. The
second version can be checked here:
https://lkml.org/lkml/2018/11/8/1005
I'm now passing the length as proposed by both Rob and Andy. I'm also
leaving the .get_named_child_node fwnode op untouched.
--
heikki
Heikki Krogerus (3):
device property: Introduce fwnode_get_name()
ACPI: property: Add acpi_fwnode_name()
of/property: Add of_fwnode_name()
drivers/acpi/property.c | 28 ++++++++++++++++++++++++++++
drivers/base/property.c | 36 ++++++++++++++++++++++++++++++++++++
drivers/of/property.c | 13 +++++++++++++
include/linux/fwnode.h | 3 +++
include/linux/property.h | 2 ++
5 files changed, 82 insertions(+)
--
2.19.2
next reply other threads:[~2018-11-28 11:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 11:59 Heikki Krogerus [this message]
2018-11-28 11:59 ` [PATCH v5 1/3] device property: Introduce fwnode_get_name() Heikki Krogerus
2018-12-07 17:24 ` Rob Herring
2018-12-10 7:36 ` Heikki Krogerus
2018-11-28 11:59 ` [PATCH v5 2/3] ACPI: property: Add acpi_fwnode_name() Heikki Krogerus
2018-11-28 11:59 ` [PATCH v5 3/3] of/property: Add of_fwnode_name() Heikki Krogerus
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=20181128115952.80890-1-heikki.krogerus@linux.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
--cc=robh@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
all inboxes | Powered by JetHome®