From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933292AbYEGTMA (ORCPT ); Wed, 7 May 2008 15:12:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1761173AbYEGTLh (ORCPT ); Wed, 7 May 2008 15:11:37 -0400 Received: from smtp1.wifiinternet.cz ([89.31.47.1]:55663 "EHLO bor.wifiinternet.cz" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1759313AbYEGTLe (ORCPT ); Wed, 7 May 2008 15:11:34 -0400 Message-ID: <4821FF0A.7090508@seznam.cz> Date: Wed, 07 May 2008 21:12:10 +0200 From: Michal Simek Reply-To: monstr@seznam.cz User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Grant Likely CC: monstr@seznam.cz, microblaze-uclinux@itee.uq.edu.au, linux-kernel@vger.kernel.org, arnd@arndb.de, linux-arch@vger.kernel.org, John Linn , john.williams@petalogix.com, matthew@wil.cx, will.newton@gmail.com, drepper@redhat.com, Paul Mackerras , Stephen Rothwell , David Miller Subject: Re: [microblaze-uclinux] [PATCH 04/56] microblaze_v2: Open firmware files References: <684c36e5ad3f598e5079e88ec195545c4a7150c2.1209897266.git.monstr@monstr.eu> <20080507160432.93FC11750046@mail35-dub.bigfish.com> <4821F794.10003@seznam.cz> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Grant, you understand I use of_device, of_platform and prom_parse. If you do diff between them they will almost the same. One small difference is in prom.c file. I hope we will move these files to drivers/of. This is not only question to me. Paul, Steve and David: Can I moved these three files to drivers/of? Michal >> Hi Steve, >> >> you are right. Microblaze don't need CONFIG_PPC_something but >> I keep this in files because it will be easier to move this to better place. >> I wanted to sort what Microblaze don't use. >> >> I need to talk with people from sparc and powerpc what we can move and where. >> I see the best way to push these files to microblaze/kernel/ and then sychronize >> them with one patch - all archs together. > > I would disagree. I think its better to push (and get merged) patches > to move the files first; then add microblaze on top of that. You can > start getting stuff merged piecemeal that way instead of relying on > getting your entire patch series merged at once. > > However, that's just my opinion, others may look at it differently. > > Cheers, > g. >