From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Grant Likely" Subject: Re: [microblaze-uclinux] [PATCH 04/56] microblaze_v2: Open firmware files Date: Wed, 7 May 2008 12:59:42 -0600 Message-ID: References: <684c36e5ad3f598e5079e88ec195545c4a7150c2.1209897266.git.monstr@monstr.eu> <20080507160432.93FC11750046@mail35-dub.bigfish.com> <4821F794.10003@seznam.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from an-out-0708.google.com ([209.85.132.242]:49253 "EHLO an-out-0708.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932700AbYEGS7n (ORCPT ); Wed, 7 May 2008 14:59:43 -0400 Received: by an-out-0708.google.com with SMTP id d40so91169and.103 for ; Wed, 07 May 2008 11:59:42 -0700 (PDT) In-Reply-To: <4821F794.10003@seznam.cz> Content-Disposition: inline Sender: linux-arch-owner@vger.kernel.org List-ID: To: monstr@seznam.cz Cc: 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, Michal Simek On Wed, May 7, 2008 at 12:40 PM, Michal Simek wrote: > 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. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd.