All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: Alban Bedel <albeu@free.fr>,
	linuxppc-dev@lists.ozlabs.org,
	Boris Brezillon <boris.brezillon@collabora.com>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
Subject: [PATCH v3 1/2] drivers/mtd: Use mtd->name when registering nvmem device
Date: Fri,  8 Feb 2019 20:44:18 +0530	[thread overview]
Message-ID: <20190208151419.1800-1-aneesh.kumar@linux.ibm.com> (raw)

With this patch, we use the mtd->name instead of concatenating the name with '0'

Fixes: c4dfa25ab307 ("mtd: add support for reading MTD devices via the nvmem API")
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
---
 drivers/mtd/mtdcore.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/mtd/mtdcore.c b/drivers/mtd/mtdcore.c
index 999b705769a8..3ef01baef9b6 100644
--- a/drivers/mtd/mtdcore.c
+++ b/drivers/mtd/mtdcore.c
@@ -507,6 +507,7 @@ static int mtd_nvmem_add(struct mtd_info *mtd)
 {
 	struct nvmem_config config = {};
 
+	config.id = -1;
 	config.dev = &mtd->dev;
 	config.name = mtd->name;
 	config.owner = THIS_MODULE;
-- 
2.20.1


             reply	other threads:[~2019-02-08 15:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-08 15:14 Aneesh Kumar K.V [this message]
2019-02-08 15:14 ` [PATCH v3 2/2] drivers/mtd: Fix device registration error Aneesh Kumar K.V
2019-02-10 12:55 ` [PATCH v3 1/2] drivers/mtd: Use mtd->name when registering nvmem device Boris Brezillon
2019-02-10 12:55   ` Boris Brezillon
2019-02-11 10:56   ` Aneesh Kumar K.V
2019-02-11 10:56     ` Aneesh Kumar K.V
2019-02-11 11:16     ` Boris Brezillon
2019-02-11 11:16       ` Boris Brezillon
2019-02-11 13:34       ` Aneesh Kumar K.V
2019-02-11 13:34         ` Aneesh Kumar K.V
  -- strict thread matches above, loose matches on Subject: below --
2019-02-11 13:33 Aneesh Kumar K.V
2019-02-11 13:33 ` Aneesh Kumar K.V

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=20190208151419.1800-1-aneesh.kumar@linux.ibm.com \
    --to=aneesh.kumar@linux.ibm.com \
    --cc=albeu@free.fr \
    --cc=boris.brezillon@collabora.com \
    --cc=linuxppc-dev@lists.ozlabs.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.