public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: <srinivas.kandagatla@linaro.org>,
	<maxime.ripard@free-electrons.com>, <wsa@the-dreams.de>,
	<broonie@kernel.org>, <vz@mleia.com>,
	<linux-kernel@vger.kernel.org>, <pantelis.antoniou@konsulko.com>,
	<bgolaszewski@baylibre.com>
Subject: Re: [PATCHv7 0/7] Convert exiting EEPROM drivers to NVMEM
Date: Wed, 02 Mar 2016 00:56:42 +0000	[thread overview]
Message-ID: <20160302005640.GA32114@kroah.com> (raw)
In-Reply-To: <1456516764-1456-1-git-send-email-andrew@lunn.ch>

On Fri, Feb 26, 2016 at 08:59:17PM +0100, Andrew Lunn wrote:
> This patch set converts the old EEPROM drivers in driver/misc/eeprom to
> use the NVMEM framework. These drivers export there content in /sys as
> read only to root, since the EEPROM may contain sensitive information.
> So the first patch adds a flag so the NVMEM framework will create its
> file in /sys as root read only.
> 
> To keep backwards compatibility with these older drivers, the contents
> of the EEPROM must be exports in sysfs in a file called eeprom in the
> devices node in sys, where as the NVMEM places them under class/nvmem.
> So add this optional backwards compatible to the framework, again
> using a flag.
> 
> Then convert the at24, at25 and 93xx46 by adding regmap support,
> removing each drivers own /sys code and registering with the NVMEM
> framework.
> 
> Lastly, the old memory accessor mechanism has been replaced with the
> nvmem equivalent.

Nice job, all now queue up.

greg k-h

  parent reply	other threads:[~2016-03-02  0:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26 19:59 [PATCHv7 0/7] Convert exiting EEPROM drivers to NVMEM Andrew Lunn
2016-02-26 19:59 ` [PATCHv7 1/7] nvmem: Add flag to export NVMEM to root only Andrew Lunn
2016-02-26 19:59 ` [PATCHv7 2/7] nvmem: Add backwards compatibility support for older EEPROM drivers Andrew Lunn
2016-02-26 19:59 ` [PATCHv7 3/7] eeprom: at24: extend driver to plug into the NVMEM framework Andrew Lunn
2016-03-02 21:46   ` Vladimir Zapolskiy
2016-03-02 21:48     ` Andrew Lunn
2016-03-02 23:03       ` Vladimir Zapolskiy
2016-02-26 19:59 ` [PATCHv7 4/7] eeprom: at25: Remove in kernel API for accessing the EEPROM Andrew Lunn
2016-02-28 21:02   ` Wolfram Sang
2016-02-26 19:59 ` [PATCHv7 5/7] eeprom: at25: extend driver to plug into the NVMEM framework Andrew Lunn
2016-03-02 21:56   ` Vladimir Zapolskiy
2016-02-26 19:59 ` [PATCHv7 6/7] eeprom: 93xx46: " Andrew Lunn
2016-03-02 22:08   ` Vladimir Zapolskiy
2016-03-02 22:26     ` Andrew Lunn
2016-03-02 23:18       ` Vladimir Zapolskiy
2016-02-26 19:59 ` [PATCHv7 7/7] misc: at24: replace memory_accessor with nvmem_device_read Andrew Lunn
2016-02-28 21:01   ` Wolfram Sang
2016-03-02  0:56 ` Greg KH [this message]
2016-03-06 12:06   ` [PATCHv7 0/7] Convert exiting EEPROM drivers to NVMEM Wolfram Sang

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=20160302005640.GA32114@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andrew@lunn.ch \
    --cc=bgolaszewski@baylibre.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=pantelis.antoniou@konsulko.com \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=vz@mleia.com \
    --cc=wsa@the-dreams.de \
    /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