From: viresh kumar <viresh.kumar@st.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Vipin KUMAR <vipin.kumar@st.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"Artem.Bityutskiy@nokia.com" <Artem.Bityutskiy@nokia.com>
Subject: Re: [PATCH] fsmc-nand: Add fsmc_nand_set_plat_data in linux/mtd/fsmc.h
Date: Fri, 25 Feb 2011 09:14:42 +0530 [thread overview]
Message-ID: <4D6725AA.3070204@st.com> (raw)
In-Reply-To: <AANLkTim3yTG-ZEZdhj=ccvd_tXm4XNG7x5uT6qS54sqQ@mail.gmail.com>
On 02/24/2011 06:08 PM, Linus Walleij wrote:
> 2011/2/23 Viresh Kumar <viresh.kumar@st.com>:
>
>> > In most of the cases partitions info, width, etc comes from board files. And
>> > device structure may be defined in machine files, common to all board files.
>> > Thus, we need to set platform data from board file, for which
>> > fsmc_nand_set_plat_data routine is required.
> Hm you create a new function, but where is it used? If it's used by a later
> patch perhaps you should make a patch series instead?
Linus,
Actually it will be used in SPEAr patches, which will be sent separately. I could
have kept it as part of that series also, but just thought to send it separately.
You want me to keep it in spear patch series instead?
--
viresh
next prev parent reply other threads:[~2011-02-25 3:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 6:49 [PATCH] fsmc-nand: Add fsmc_nand_set_plat_data in linux/mtd/fsmc.h Viresh Kumar
2011-02-24 12:38 ` Linus Walleij
2011-02-25 3:44 ` viresh kumar [this message]
2011-02-25 8:39 ` Linus Walleij
2011-02-25 11:07 ` Artem Bityutskiy
2011-02-25 11:11 ` viresh kumar
2011-02-25 11:12 ` Artem Bityutskiy
2011-02-25 11:11 ` Artem Bityutskiy
2011-02-25 11:22 ` viresh kumar
2011-02-25 11:25 ` Artem Bityutskiy
2011-02-25 11:43 ` viresh kumar
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=4D6725AA.3070204@st.com \
--to=viresh.kumar@st.com \
--cc=Artem.Bityutskiy@nokia.com \
--cc=dwmw2@infradead.org \
--cc=linus.walleij@linaro.org \
--cc=linux-mtd@lists.infradead.org \
--cc=vipin.kumar@st.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 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.