public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@linuxcare.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Architecture-specific include files
Date: 26 Apr 2001 03:51:39 +0200	[thread overview]
Message-ID: <d34rvc2ztg.fsf@lxplus015.cern.ch> (raw)
In-Reply-To: <20010422210118.Z18464@parcelfarce.linux.theplanet.co.uk>
In-Reply-To: Matthew Wilcox's message of "Sun, 22 Apr 2001 21:01:18 +0100"

>>>>> "Matthew" == Matthew Wilcox <matthew@wil.cx> writes:

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-$ARCH
Matthew> to arch/$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?

Jes

  parent reply	other threads:[~2001-04-26  1:52 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 [this message]
2001-04-27 10:47   ` Pavel Machek

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=d34rvc2ztg.fsf@lxplus015.cern.ch \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox