From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wy0-f177.google.com ([74.125.82.177]) by canuck.infradead.org with esmtps (Exim 4.72 #1 (Red Hat Linux)) id 1PsviE-00039T-L4 for linux-mtd@lists.infradead.org; Fri, 25 Feb 2011 11:19:55 +0000 Received: by wyf23 with SMTP id 23so1542048wyf.36 for ; Fri, 25 Feb 2011 03:19:53 -0800 (PST) Subject: Re: [PATCH] fsmc-nand: Add fsmc_nand_set_plat_data in linux/mtd/fsmc.h From: Artem Bityutskiy To: viresh kumar In-Reply-To: <4D678E56.8050908@st.com> References: <4D6725AA.3070204@st.com> <1298632021.2798.62.camel@localhost> <4D678E56.8050908@st.com> Content-Type: text/plain; charset="UTF-8" Date: Fri, 25 Feb 2011 13:12:20 +0200 Message-ID: <1298632340.2798.68.camel@localhost> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Cc: Vipin KUMAR , "linux-mtd@lists.infradead.org" , Linus Walleij , "dwmw2@infradead.org" Reply-To: dedekind1@gmail.com List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Fri, 2011-02-25 at 16:41 +0530, viresh kumar wrote: > On 02/25/2011 04:37 PM, Artem Bityutskiy wrote: > > On Fri, 2011-02-25 at 09:14 +0530, viresh kumar wrote: > >> > On 02/24/2011 06:08 PM, Linus Walleij wrote: > >>> > > 2011/2/23 Viresh Kumar : > >>> > > > >>>>> > >> > 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? > > I think this is important piece of information which should be in the > > patch commit message. > > Ok. I will resend it. To elaborate, imagine I put this patch to my l2 tree, then David has the same question when he decides whether to pick it or not. -- Best Regards, Artem Bityutskiy (Артём Битюцкий)