From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: Boris Brezillon <boris.brezillon@collabora.com>
Cc: linuxppc-dev@lists.ozlabs.org, Alban Bedel <albeu@free.fr>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH v3 1/2] drivers/mtd: Use mtd->name when registering nvmem device
Date: Mon, 11 Feb 2019 19:04:57 +0530 [thread overview]
Message-ID: <c7885c03-6cd5-d6ba-b2f4-63e2d1f03cd4@linux.ibm.com> (raw)
In-Reply-To: <20190211121628.30c22370@collabora.com>
On 2/11/19 4:46 PM, Boris Brezillon wrote:
> On Mon, 11 Feb 2019 16:26:38 +0530
> "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com> wrote:
>
>> On 2/10/19 6:25 PM, Boris Brezillon wrote:
>>> Hello Aneesh,
>>>
>>> On Fri, 8 Feb 2019 20:44:18 +0530
>>> "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com> wrote:
>>>
>>>> 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>
>>>
>>> You forgot to Cc the MTD ML and maintainers. Can you please send a new
>>> version?
>>>
>>
>> linux-mtd list is on CC: Is that not sufficient?
>
> Not in your original email, I added it in my reply.
>
Sorry about that. I will now resend with linux-mtd on CC: I missed that
earlier.
-aneesh
next prev parent reply other threads:[~2019-02-11 13:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 15:14 [PATCH v3 1/2] drivers/mtd: Use mtd->name when registering nvmem device Aneesh Kumar K.V
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-11 10:56 ` Aneesh Kumar K.V
2019-02-11 11:16 ` Boris Brezillon
2019-02-11 13:34 ` Aneesh Kumar K.V [this message]
-- strict thread matches above, loose matches on Subject: below --
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=c7885c03-6cd5-d6ba-b2f4-63e2d1f03cd4@linux.ibm.com \
--to=aneesh.kumar@linux.ibm.com \
--cc=albeu@free.fr \
--cc=boris.brezillon@collabora.com \
--cc=linux-mtd@lists.infradead.org \
--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 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).