DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=q701VdfWIaOVhG3hgcMA6CDugZi+ywqdhF4JApiQEgbRGBDEuyJ/IFeBJpGsKjkBNm
         4q01zQSMCzAcUAdUSzNZR/paC6tJY1D0ysRAXlUzUYDxmtw5j05TDfbKwYVKmjiOT8Fb
         tkZM4En1r+55FAMnqf3YBZUZGnmFeE+ODIpAM=
Message-ID: <8bd0f97a0810211046n2e32868fu1a58cc9123da7c6d@mail.gmail.com>
Date: Tue, 21 Oct 2008 13:46:18 -0400
From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Jesper Nilsson" <jesper.nilsson@axis.com>
Subject: Re: [RFC] CRIS: Move header files from include to arch/cris
Cc: "Sam Ravnborg" <sam@ravnborg.org>, LKML <linux-kernel@vger.kernel.org>,
       "Mikael Starvik" <mikael.starvik@axis.com>,
       "Bryan Wu" <Bryan.Wu@analog.com>
In-Reply-To: <20081021164211.GG24715@axis.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20081021164211.GG24715@axis.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 768
Lines: 16

On Tue, Oct 21, 2008 at 12:42, Jesper Nilsson <jesper.nilsson@axis.com> wrote:
> That means that the machine dependent header files are moved to
> arch/cris/mach-{fs,a3}/include, while the common and architecture
> dependent files are moved to arch/cris/include.
>
> It is mainly this I'd like some input on, since most other ports
> that have moved their header files have put all headers in arch/*/include.

that seems like a fairly obvious good idea to me ... i'm thinking we
should do it for Blackfin as well ...
-mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/