devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeppe Ledet-Pedersen <jlp@gomspace.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: lee.jones@linaro.org, arnd@arndb.de, gregkh@linuxfoundation.org,
	a.zummo@towertech.it, robh+dt@kernel.org, pawel.moll@arm.com,
	mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
	galak@codeaurora.org, rtc-linux@googlegroups.com,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] misc: eeprom: add Cypress FM33256B FRAM driver
Date: Tue, 26 Apr 2016 14:08:37 +0200	[thread overview]
Message-ID: <571F5A45.2050405@gomspace.com> (raw)
In-Reply-To: <20160421235429.GA6086@piout.net>

On 22/04/16 01:54, Alexandre Belloni wrote:
> Hi,

Hi Alexandre,

> On 20/04/2016 at 13:07:50 +0200, Jeppe Ledet-Pedersen wrote :
>> Signed-off-by: Jeppe Ledet-Pedersen <jlp@gomspace.com>
>> ---
>>  MAINTAINERS                         |   1 +
>>  drivers/misc/eeprom/Kconfig         |  12 ++++
>>  drivers/misc/eeprom/Makefile        |   1 +
>>  drivers/misc/eeprom/fm33256b-fram.c | 110 ++++++++++++++++++++++++++++++++++++
>>  4 files changed, 124 insertions(+)
>>  create mode 100644 drivers/misc/eeprom/fm33256b-fram.c
>>
> 
> There is now an nvmem framework that will allow you to easily have both
> an in-kernel and a userspace interface.

Thanks, I'll take a look at nvmem. It does look like a much better fit.

-Jeppe

  reply	other threads:[~2016-04-26 12:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20 11:07 [PATCH 0/3] Cypress FM33256B processor companion support Jeppe Ledet-Pedersen
     [not found] ` <1461150471-23163-1-git-send-email-jlp-jTq9jD7AHYRWk0Htik3J/w@public.gmane.org>
2016-04-20 11:07   ` [PATCH 1/3] mfd: add Cypress FM33256B Processor Companion driver Jeppe Ledet-Pedersen
     [not found]     ` <1461150471-23163-2-git-send-email-jlp-jTq9jD7AHYRWk0Htik3J/w@public.gmane.org>
2016-04-22  0:47       ` kbuild test robot
2016-04-22 19:32       ` Rob Herring
2016-04-22 20:11         ` Alexandre Belloni
     [not found]           ` <20160422201153.GB17051-m++hUPXGwpdeoWH0uzbU5w@public.gmane.org>
2016-04-26 14:31             ` Jeppe Ledet-Pedersen
     [not found]               ` <571F7BD2.60201-jTq9jD7AHYRWk0Htik3J/w@public.gmane.org>
2016-05-03  8:14                 ` Alexandre Belloni
2016-04-26 14:42         ` Jeppe Ledet-Pedersen
2016-04-20 11:07   ` [PATCH 2/3] misc: eeprom: add Cypress FM33256B FRAM driver Jeppe Ledet-Pedersen
2016-04-21 23:54     ` Alexandre Belloni
2016-04-26 12:08       ` Jeppe Ledet-Pedersen [this message]
2016-04-20 11:07   ` [PATCH 3/3] rtc: add Cypress FM33256B RTC driver Jeppe Ledet-Pedersen
2016-04-21 23:44     ` Alexandre Belloni
     [not found]       ` <20160421234400.GG29844-m++hUPXGwpdeoWH0uzbU5w@public.gmane.org>
2016-04-26 12:17         ` Jeppe Ledet-Pedersen

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=571F5A45.2050405@gomspace.com \
    --to=jlp@gomspace.com \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=rtc-linux@googlegroups.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).