public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Arnd Bergmann <arnd@arndb.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Rob Herring <robh@kernel.org>,
	"Gustavo A . R . Silva" <gustavo@embeddedor.com>,
	Devang Panchal <devang.panchal@softnautics.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: linux-kernel@vger.kernel.org,
	Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: [PATCH 0/2] eeprom: use devres for nvmem providers
Date: Mon, 10 Sep 2018 09:44:02 +0200	[thread overview]
Message-ID: <20180910074404.8041-1-brgl@bgdev.pl> (raw)

From: Bartosz Golaszewski <bgolaszewski@baylibre.com>

While working on the nvmem framework recently I noticed that there are
many providers that don't use the devm variant of nvmem_register().
This series contains relevant updates for eeprom drivers.

Bartosz Golaszewski (2):
  eeprom: eeprom_93xx46: use resource management
  eeprom: at25: use devm_nvmem_register()

 drivers/misc/eeprom/at25.c          | 3 +--
 drivers/misc/eeprom/eeprom_93xx46.c | 7 ++-----
 2 files changed, 3 insertions(+), 7 deletions(-)

-- 
2.18.0


             reply	other threads:[~2018-09-10  7:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-10  7:44 Bartosz Golaszewski [this message]
2018-09-10  7:44 ` [PATCH 1/2] eeprom: eeprom_93xx46: use resource management Bartosz Golaszewski
2018-09-10  7:44 ` [PATCH 2/2] eeprom: at25: use devm_nvmem_register() Bartosz Golaszewski
2018-09-10  7:50 ` [PATCH 0/2] eeprom: use devres for nvmem providers Srinivas Kandagatla
2018-09-10  7:54   ` Bartosz Golaszewski
2018-09-10  7:59     ` Srinivas Kandagatla
2018-09-10  8:08       ` Bartosz Golaszewski

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=20180910074404.8041-1-brgl@bgdev.pl \
    --to=brgl@bgdev.pl \
    --cc=arnd@arndb.de \
    --cc=bgolaszewski@baylibre.com \
    --cc=devang.panchal@softnautics.com \
    --cc=geert+renesas@glider.be \
    --cc=gregkh@linuxfoundation.org \
    --cc=gustavo@embeddedor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=srinivas.kandagatla@linaro.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