From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Sascha Hauer <s.hauer@pengutronix.de>, linux-kernel@vger.kernel.org
Cc: kernel@pengutronix.de, linux-mtd@lists.infradead.org
Subject: Re: nvmem creates multiple devices with the same name
Date: Tue, 21 May 2019 10:02:32 +0100 [thread overview]
Message-ID: <a9ccac90-7b2f-41da-2ca9-ca3bba52781b@linaro.org> (raw)
In-Reply-To: <20190521085641.i6g5aijwa5zbolah@pengutronix.de>
On 21/05/2019 09:56, Sascha Hauer wrote:
> . Are there any suggestions how to register the nvmem devices
> with a different name?
struct nvmem_config provides id field for this purpose, this will be
used by nvmem to set the device name space along with name field.
--srini
next prev parent reply other threads:[~2019-05-21 9:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 8:56 nvmem creates multiple devices with the same name Sascha Hauer
2019-05-21 9:02 ` Srinivas Kandagatla [this message]
2019-05-21 9:21 ` Sascha Hauer
2019-07-01 8:06 ` Sascha Hauer
2019-07-02 16:54 ` Srinivas Kandagatla
2019-07-08 7:14 ` Sascha Hauer
2019-07-02 18:59 ` Boris Brezillon
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=a9ccac90-7b2f-41da-2ca9-ca3bba52781b@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=s.hauer@pengutronix.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;
as well as URLs for NNTP newsgroup(s).