From: Sam Ravnborg <sam@ravnborg.org>
To: Jesper Nilsson <Jesper.Nilsson@axis.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Mikael Starvik <mikael.starvik@axis.com>
Subject: Re: [PATCH] [CRIS] Move header files from include to arch/cris/include.
Date: Wed, 29 Oct 2008 19:53:13 +0100 [thread overview]
Message-ID: <20081029185313.GA22105@uranus.ravnborg.org> (raw)
In-Reply-To: <20081029173420.GM4608@axis.com>
On Wed, Oct 29, 2008 at 06:34:20PM +0100, Jesper Nilsson wrote:
> On Tue, Oct 21, 2008 at 06:42:11PM +0200, Jesper Nilsson wrote:
> > Hi,
> >
> > I'm looking for some feedback on the changes in the branch include_move
> > at the git-tree:
> >
> > git://repo.or.cz/cris-mirror.git include_move
> >
> > I've performed the move of the CRIS headers using the ARM and Blackfin
> > ports as a pattern.
> >
> > 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.
>
> After some soul-searching I've changed this, and moved all header
> files into arch/cris/include. The most telling argument was that
> the CRIS port wouldn't have anything other than include files in
> the arch/cris/mach-* directories.
>
> If that changes some time in the future, it is a simple operation
> moving the machine dependent header files there.
>
> Since the complete patch is too large to post, I'm not including
> the diff of the files moved, only the files changed.
Hi Jesper.
I have looked at the diffstat and the patches and this is a
great improvement in readability of the cris stuff.
It would be good to get this in mainline as fast as possible.
Can I ask you to prepare to git trees to pull from and ask
Linus to pull it.
First tree should be the header move only and if you can
convince him it would be great to take the next two patches
so add them to another tree.
You can add an:
Acked-by: Sam Ravnborg <sam@ravnborg.org>
on all three patches.
Sam
next prev parent reply other threads:[~2008-10-29 18:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 16:42 [RFC] CRIS: Move header files from include to arch/cris Jesper Nilsson
2008-10-21 17:46 ` Mike Frysinger
2008-10-21 19:17 ` Jesper Nilsson
2008-10-21 19:23 ` Mike Frysinger
2008-10-22 2:38 ` Bryan Wu
2008-10-22 2:36 ` Bryan Wu
2008-10-22 3:11 ` Mike Frysinger
2008-10-29 17:34 ` [PATCH] [CRIS] Move header files from include to arch/cris/include Jesper Nilsson
2008-10-29 18:53 ` Sam Ravnborg [this message]
2008-10-30 12:12 ` Jesper Nilsson
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=20081029185313.GA22105@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=Jesper.Nilsson@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikael.starvik@axis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox