From: David Brown <davidb@codeaurora.org>
To: Murali Nalajala <mnalajal@codeaurora.org>
Cc: dwmw2@infradead.org, linux-arm-msm@vger.kernel.org,
linux-mtd@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Dima Zavin <dima@android.com>
Subject: Re: [PATCH V2 1/2] mtd: nand: Allow NAND chip ids to be included standalone.
Date: Thu, 14 Apr 2011 16:33:02 -0700 [thread overview]
Message-ID: <8ya39lk5ryp.fsf@huya.qualcomm.com> (raw)
In-Reply-To: <1299542935-20291-1-git-send-email-mnalajal@codeaurora.org> (Murali Nalajala's message of "Tue, 8 Mar 2011 05:38:55 +0530")
On Mon, Mar 07 2011, Murali Nalajala wrote:
> Lets non-standard NAND drivers take advantage of known NAND
> chip information.
>
> The initial development of msm nand driver, driver uses the supported
> NAND devices information as a hardcoded table. Remove the existing
> hardcoded supported flash device table and read the flash device
> information from the flash id table which are part of the mtd subsystem.
>
> Signed-off-by: Dima Zavin <dima@android.com>
> Signed-off-by: Murali Nalajala <mnalajal@codeaurora.org>
Acked-by: David Brown <davidb@codeaurora.org>
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
WARNING: multiple messages have this Message-ID (diff)
From: David Brown <davidb@codeaurora.org>
To: Murali Nalajala <mnalajal@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org, dwmw2@infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-mtd@lists.infradead.org, Dima Zavin <dima@android.com>
Subject: Re: [PATCH V2 1/2] mtd: nand: Allow NAND chip ids to be included standalone.
Date: Thu, 14 Apr 2011 16:33:02 -0700 [thread overview]
Message-ID: <8ya39lk5ryp.fsf@huya.qualcomm.com> (raw)
In-Reply-To: <1299542935-20291-1-git-send-email-mnalajal@codeaurora.org> (Murali Nalajala's message of "Tue, 8 Mar 2011 05:38:55 +0530")
On Mon, Mar 07 2011, Murali Nalajala wrote:
> Lets non-standard NAND drivers take advantage of known NAND
> chip information.
>
> The initial development of msm nand driver, driver uses the supported
> NAND devices information as a hardcoded table. Remove the existing
> hardcoded supported flash device table and read the flash device
> information from the flash id table which are part of the mtd subsystem.
>
> Signed-off-by: Dima Zavin <dima@android.com>
> Signed-off-by: Murali Nalajala <mnalajal@codeaurora.org>
Acked-by: David Brown <davidb@codeaurora.org>
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
WARNING: multiple messages have this Message-ID (diff)
From: davidb@codeaurora.org (David Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 1/2] mtd: nand: Allow NAND chip ids to be included standalone.
Date: Thu, 14 Apr 2011 16:33:02 -0700 [thread overview]
Message-ID: <8ya39lk5ryp.fsf@huya.qualcomm.com> (raw)
In-Reply-To: <1299542935-20291-1-git-send-email-mnalajal@codeaurora.org> (Murali Nalajala's message of "Tue, 8 Mar 2011 05:38:55 +0530")
On Mon, Mar 07 2011, Murali Nalajala wrote:
> Lets non-standard NAND drivers take advantage of known NAND
> chip information.
>
> The initial development of msm nand driver, driver uses the supported
> NAND devices information as a hardcoded table. Remove the existing
> hardcoded supported flash device table and read the flash device
> information from the flash id table which are part of the mtd subsystem.
>
> Signed-off-by: Dima Zavin <dima@android.com>
> Signed-off-by: Murali Nalajala <mnalajal@codeaurora.org>
Acked-by: David Brown <davidb@codeaurora.org>
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2011-04-14 23:30 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 0:08 [PATCH V2 1/2] mtd: nand: Allow NAND chip ids to be included standalone Murali Nalajala
2011-03-08 0:08 ` Murali Nalajala
2011-03-08 0:08 ` Murali Nalajala
2011-03-08 7:50 ` Artem Bityutskiy
2011-03-08 7:50 ` Artem Bityutskiy
2011-03-08 7:50 ` Artem Bityutskiy
2011-03-08 17:41 ` Murali Nalajala
2011-03-08 17:41 ` Murali Nalajala
2011-03-08 17:41 ` Murali Nalajala
2011-03-21 6:39 ` Murali Nalajala
2011-03-21 6:39 ` Murali Nalajala
2011-03-21 6:39 ` Murali Nalajala
2011-03-21 7:12 ` Artem Bityutskiy
2011-03-21 7:12 ` Artem Bityutskiy
2011-03-21 7:12 ` Artem Bityutskiy
2011-03-21 7:58 ` Murali Nalajala
2011-03-21 7:58 ` Murali Nalajala
2011-03-21 7:58 ` Murali Nalajala
2011-03-22 6:41 ` Murali Nalajala
2011-03-22 6:41 ` Murali Nalajala
2011-03-22 6:41 ` Murali Nalajala
2011-03-22 8:11 ` Artem Bityutskiy
2011-03-22 8:11 ` Artem Bityutskiy
2011-03-22 8:11 ` Artem Bityutskiy
2011-04-06 4:38 ` Murali Nalajala
2011-04-06 4:38 ` Murali Nalajala
2011-04-06 4:38 ` Murali Nalajala
2011-04-06 7:21 ` Artem Bityutskiy
2011-04-06 7:21 ` Artem Bityutskiy
2011-04-06 7:21 ` Artem Bityutskiy
2011-04-07 6:28 ` Dima Zavin
2011-04-07 6:28 ` Dima Zavin
2011-04-07 6:28 ` Dima Zavin
2011-04-14 23:33 ` David Brown [this message]
2011-04-14 23:33 ` David Brown
2011-04-14 23:33 ` David Brown
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=8ya39lk5ryp.fsf@huya.qualcomm.com \
--to=davidb@codeaurora.org \
--cc=dima@android.com \
--cc=dwmw2@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mnalajal@codeaurora.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.