From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: Jiri Prchal <jiri.prchal@aksignal.cz>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>,
Christian Eggers <ceggers@arri.de>, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v6 1/5] nvmem: eeprom: at25: prepare basics for FRAM support
Date: Mon, 7 Jun 2021 15:05:13 +0200 [thread overview]
Message-ID: <59450413-b370-3615-b2e7-18bee71e5e0d@metux.net> (raw)
In-Reply-To: <20210607082638.52409-2-jiri.prchal@aksignal.cz>
On 07.06.21 10:26, Jiri Prchal wrote:
> Added enum and string for FRAM to expose it as "fram".
Is "at25" in subject of this patch really correct ?
Seems that patch is against to nvmen core, not at25 driver.
--mtx
--
---
Hinweis: unverschlüsselte E-Mails können leicht abgehört und manipuliert
werden ! Für eine vertrauliche Kommunikation senden Sie bitte ihren
GPG/PGP-Schlüssel zu.
---
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287
next prev parent reply other threads:[~2021-06-07 13:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 8:26 [PATCH v6 0/5] add support for FRAM Jiri Prchal
2021-06-07 8:26 ` [PATCH v6 1/5] nvmem: eeprom: at25: prepare basics for FRAM support Jiri Prchal
2021-06-07 13:05 ` Enrico Weigelt, metux IT consult [this message]
2021-06-07 8:26 ` [PATCH v6 2/5] nvmem: eeprom: at25: add support for FRAM Jiri Prchal
2021-06-07 8:26 ` [PATCH v6 3/5] nvmem: eeprom: add documentation " Jiri Prchal
2021-06-07 8:26 ` [PATCH v6 4/5] nvmem: eeprom: at25: export FRAM serial num Jiri Prchal
2021-06-07 9:31 ` Greg Kroah-Hartman
2021-06-07 9:31 ` Greg Kroah-Hartman
2021-06-07 8:26 ` [PATCH v6 5/5] nvmem: eeprom: add documentation of sysfs sernum file Jiri Prchal
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=59450413-b370-3615-b2e7-18bee71e5e0d@metux.net \
--to=lkml@metux.net \
--cc=arnd@arndb.de \
--cc=ceggers@arri.de \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.