From: Sergei Shtylyov <sshtylyov@mvista.com>
To: "Manjunathappa, Prakash" <prakash.pm@ti.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"davinci-linux-open-source@linux.davincidsp.com"
<davinci-linux-open-source@linux.davincidsp.com>,
Russell King <linux@arm.linux.org.uk>,
Samuel Ortiz <sameo@linux.intel.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH v2 3/3] arm: da830: move NAND and NOR devices as aemif MFD slaves
Date: Mon, 30 Jan 2012 14:40:31 +0400 [thread overview]
Message-ID: <4F26739F.2070305@mvista.com> (raw)
In-Reply-To: <A73F36158E33644199EB82C5EC81C7BC3175BD35@DBDE01.ent.ti.com>
Hello.
On 30-01-2012 10:58, Manjunathappa, Prakash wrote:
>>> NAND and NOR device are made as aemif devices slave, hence device
>>> registration achieved via aemif MFD driver.
>>> Signed-off-by: Manjunathappa, Prakash<prakash.pm@ti.com>
>>> ---
>>> Since v1:
>>> Patch is generated using -M option.
>>> arch/arm/mach-davinci/board-da830-evm.c | 31 +++++++++++++++++++++++--------
>>> 1 files changed, 23 insertions(+), 8 deletions(-)
>> Why only this file? Don't other board files have NAND/NOR devices?
> Yes I thought of sending board-da850 changes in separate patch. Should I have to send those changes also in this patch?
There's also board-dm*.c files. I'd done them all in the same patch.
> Thanks,
> Prakash
WBR, Sergei
next prev parent reply other threads:[~2012-01-30 10:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 10:25 [PATCH v2 1/3] arm:davinci: prepare to move aemif driver to drivers/mfd Manjunathappa, Prakash
2012-01-25 10:25 ` [PATCH v2 2/3] arm:davinci: Move emif driver to drivers/mfd from mach-davinci folder Manjunathappa, Prakash
2012-01-25 10:25 ` [PATCH v2 3/3] arm: da830: move NAND and NOR devices as aemif MFD slaves Manjunathappa, Prakash
2012-01-25 14:51 ` Sergei Shtylyov
2012-01-30 6:58 ` Manjunathappa, Prakash
2012-01-30 10:40 ` Sergei Shtylyov [this message]
2012-01-31 7:11 ` Manjunathappa, Prakash
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=4F26739F.2070305@mvista.com \
--to=sshtylyov@mvista.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=dwmw2@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=prakash.pm@ti.com \
--cc=sameo@linux.intel.com \
/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).