mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: Al Viro <viro@ftp.linux.org.uk>,
	Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] minimal alpha pt_regs fixes
Date: Sat, 7 Oct 2006 20:27:08 +0200	[thread overview]
Message-ID: <20061007182708.GB5937@uranus.ravnborg.org> (raw)
In-Reply-To: <4527C2F7.2010102@garzik.org>

On Sat, Oct 07, 2006 at 11:08:39AM -0400, Jeff Garzik wrote:
> Al Viro wrote:
> >diff --git a/include/asm-alpha/irq_regs.h b/include/asm-alpha/irq_regs.h
> >new file mode 100644
> >index 0000000..3dd9c0b
> >--- /dev/null
> >+++ b/include/asm-alpha/irq_regs.h
> >@@ -0,0 +1 @@
> >+#include <asm-generic/irq_regs.h>
> 
> 
> ACK, of course, but I wonder if we can do something about these 1-line 
> header files.

It would be even more simple and future proof if we could in
some way do it so "#include <foo/bar.h>" would pick up bar.h from
asm-$(ARCH) if it exists and otherwise pick up asm-generic/bar.h.

Then we could include the generic one in asm-generic and
all architectures would include it except those that provide their
own variant. The asm-$(ARCH) specific files would need a way to include
the asm-generic version.

I have no idea handy for how to actually implment this but wanted
just to share the idea.
The trade-off is that if it gets too iplicit then suddenly users will
loose overview of how it works.

	Sam

  parent reply	other threads:[~2006-10-07 18:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-07 13:17 Al Viro
2006-10-07 15:08 ` Jeff Garzik
2006-10-07 15:14   ` Al Viro
2006-10-07 17:49   ` Linus Torvalds
2006-10-07 18:27   ` Sam Ravnborg [this message]
2006-10-07 23:35     ` Kyle Moffett

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=20061007182708.GB5937@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=akpm@osdl.org \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=viro@ftp.linux.org.uk \
    /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

Powered by JetHome