From: Pavel Machek <pavel@suse.cz>
To: Jes Sorensen <jes@linuxcare.com>
Cc: Matthew Wilcox <matthew@wil.cx>, linux-kernel@vger.kernel.org
Subject: Re: Architecture-specific include files
Date: Fri, 27 Apr 2001 10:47:24 +0000 [thread overview]
Message-ID: <20010427104724.B37@(none)> (raw)
In-Reply-To: <20010422210118.Z18464@parcelfarce.linux.theplanet.co.uk> <d34rvc2ztg.fsf@lxplus015.cern.ch>
In-Reply-To: <d34rvc2ztg.fsf@lxplus015.cern.ch>; from jes@linuxcare.com on Thu, Apr 26, 2001 at 03:51:39AM +0200
Hi!
> Matthew> Something which came up in one of the hallway discussions at
> Matthew> the kernelsummit was that a lot of the architecture
> Matthew> maintainers would find it more convenient if the
> Matthew> arch-specific header files were moved from include/asm-
> Matthew> to arch//include. Since we use a symlink _anyway_, no
> Matthew> global changes to include statements are necessary, we'd
> Matthew> merely need to change Makefile from
>
> [snip]
>
> Matthew> Would anyone have a problem with this change? It'll make for
> Matthew> a hell of a big patch from Linus, but it really will simplify
> Matthew> the lives of the architecture maintainers.
>
> I don't see what it saves, except for the fact you just have to run
> diff -urN once instead of twice when you want to send Linus a large
> diff. Or am I missing something?
Saving one diff urN is nice, plus you can distribute your architecture
as tar file more easily, plus it is easier to put just your arch in cvs.
I like it.
Pavel
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
prev parent reply other threads:[~2001-04-29 11:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-22 20:01 Architecture-specific include files Matthew Wilcox
2001-04-22 22:23 ` Jeff Dike
2001-04-26 1:51 ` Jes Sorensen
2001-04-27 10:47 ` Pavel Machek [this message]
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='20010427104724.B37@(none)' \
--to=pavel@suse.cz \
--cc=jes@linuxcare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.