linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Paul Herbert <kph@platinasystems.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Len Brown <lenb@kernel.org>,
	linux-acpi@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	Frank Rowand <frowand.list@gmail.com>,
	devicetree@vger.kernel.org,
	Tom Grennan <tgrennan@platinasystems.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/1] nvmem: Change to unified property interface
Date: Tue, 30 Mar 2021 09:18:14 -0700	[thread overview]
Message-ID: <20210330161814.3144336-1-kph@platinasystems.com> (raw)
In-Reply-To: <20210329223827.2851916-1-kph@platinasystems.com>

nvmem: Change to unified property interface

Change from using device tree (Open Firmware) APIs to the unified
'fwnode' interface.

Change of_nvmem_cell_get() to fwnode_nvmem_cell_get(), and add a
wrapper for of_nvmem_cell_get().

Change of_nvmem_device_get() to fwnode_nvmem_device_get(). There
are no known accessors to the OF interface, so no need for a wrapper.

The first version of this patch incorrectly had a wrapper for
of_nvmem_device_get(), even though the comments about the patch
not needing this were correct.

The second version of this patch had an incorrect return type for
of_nvmem_device_get().


  parent reply	other threads:[~2021-03-30 16:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29 22:38 [PATCH] nvmem: Change to unified property interface Kevin Paul Herbert
2021-03-30  3:21 ` kernel test robot
2021-03-30  4:26 ` [PATCH v2] " Kevin Paul Herbert
2021-03-30  4:28 ` Kevin Paul Herbert
2021-03-30  4:34 ` Kevin Paul Herbert
2021-03-30  4:57 ` [PATCH] " kernel test robot
2021-03-30 10:43 ` kernel test robot
2021-03-30 16:18 ` Kevin Paul Herbert [this message]
2021-03-30 16:18 ` [PATCH v3 1/1] " Kevin Paul Herbert

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=20210330161814.3144336-1-kph@platinasystems.com \
    --to=kph@platinasystems.com \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=robh+dt@kernel.org \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=tgrennan@platinasystems.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).