From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jiri Prchal <jiri.prchal@aksignal.cz>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Christian Eggers <ceggers@arri.de>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v10 0/4] add support for FRAM
Date: Fri, 11 Jun 2021 12:25:33 +0200 [thread overview]
Message-ID: <YMM6Hdw5mdK8LXQe@kroah.com> (raw)
In-Reply-To: <20210611094601.95131-1-jiri.prchal@aksignal.cz>
On Fri, Jun 11, 2021 at 11:45:57AM +0200, Jiri Prchal wrote:
> Adds support for Cypress FRAMs.
>
> Jiri Prchal (4):
> nvmem: prepare basics for FRAM support
> nvmem: eeprom: at25: add support for FRAM
> dt-bindings: nvmem: at25: add for FRAM support
> nvmem: eeprom: at25: export FRAM serial num
>
> .../ABI/testing/sysfs-class-spi-eeprom | 19 +++
> .../devicetree/bindings/eeprom/at25.yaml | 31 +++-
> drivers/misc/eeprom/Kconfig | 5 +-
> drivers/misc/eeprom/at25.c | 161 ++++++++++++++----
> drivers/nvmem/core.c | 4 +
> include/linux/nvmem-provider.h | 1 +
> 6 files changed, 183 insertions(+), 38 deletions(-)
> create mode 100644 Documentation/ABI/testing/sysfs-class-spi-eeprom
>
> --
> 2.25.1
>
Looks good to me, now queued up. Thanks for sticking with this!
greg k-h
prev parent reply other threads:[~2021-06-11 10:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 9:45 [PATCH v10 0/4] add support for FRAM Jiri Prchal
2021-06-11 9:45 ` [PATCH v10 1/4] nvmem: prepare basics for FRAM support Jiri Prchal
2021-06-11 9:45 ` [PATCH v10 2/4] nvmem: eeprom: at25: add support for FRAM Jiri Prchal
2021-06-16 18:59 ` kernel test robot
2021-06-22 7:44 ` kernel test robot
2021-06-11 9:46 ` [PATCH v10 3/4] dt-bindings: nvmem: at25: add for FRAM support Jiri Prchal
2021-06-11 9:46 ` [PATCH v10 4/4] nvmem: eeprom: at25: export FRAM serial num Jiri Prchal
2021-06-16 20:10 ` kernel test robot
2021-06-22 9:33 ` kernel test robot
2021-06-11 10:25 ` Greg Kroah-Hartman [this message]
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=YMM6Hdw5mdK8LXQe@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=ceggers@arri.de \
--cc=devicetree@vger.kernel.org \
--cc=jiri.prchal@aksignal.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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