All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Paul Mundt <lethal@linux-sh.org>, Andrew Morton <akpm@osdl.org>,
	linux-arch@vger.kernel.org
Subject: Re: irq-type-flags.patch
Date: Wed, 9 Nov 2005 08:26:59 -0700	[thread overview]
Message-ID: <20051109152659.GD27540@parisc-linux.org> (raw)
In-Reply-To: <20051109144758.GE4712@flint.arm.linux.org.uk>

On Wed, Nov 09, 2005 at 02:47:58PM +0000, Russell King wrote:
> On Wed, Nov 09, 2005 at 06:49:32AM -0700, Matthew Wilcox wrote:
> > On Wed, Nov 09, 2005 at 03:30:23PM +0200, Paul Mundt wrote:
> > > > +#define SA_TRIGGER_LOW		0x00000004
> > > > +#define SA_TRIGGER_RISING	0x00000002
> > > > +#define SA_TRIGGER_FALLING	0x00000001
> > > It probably makes sense to move SA_TRIGGER here as well, as it's going to
> > > be a pretty common mask. Otherwise everyone that plans to make use of
> > > this will likely end up duplicating it.
> > 
> > Are there any other architectures that plan to make use of this?
> 
> Just to be clear - the primary reason I'm putting these in a shared
> file is that we don't want to add #ifdefs to drivers (which is what
> would be necessary if it was placed in asm-arm.)

Certainly.  The question is whether it makes sense to put the SA_TRIGGER
define (being the | of all these) in arch files or in the common files.
And it sounds like since SH also needs to use this, that should also go
in adjacent to the SA_TRIGGER_* defines.

  reply	other threads:[~2005-11-09 15:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-09  3:10 irq-type-flags.patch Andrew Morton
2005-11-09  9:26 ` irq-type-flags.patch William Lee Irwin III
2005-11-09 13:20 ` irq-type-flags.patch David Howells
2005-11-09 13:24   ` irq-type-flags.patch Russell King
2005-11-09 15:13     ` irq-type-flags.patch David Howells
2005-11-09 15:27       ` irq-type-flags.patch Russell King
2005-11-09 16:07         ` irq-type-flags.patch David Howells
2005-11-09 13:30 ` irq-type-flags.patch Paul Mundt
2005-11-09 13:49   ` irq-type-flags.patch Matthew Wilcox
2005-11-09 14:40     ` irq-type-flags.patch Paul Mundt
2005-11-09 14:47     ` irq-type-flags.patch Russell King
2005-11-09 15:26       ` Matthew Wilcox [this message]
2005-11-09 15:28         ` irq-type-flags.patch Russell King
2005-11-10 14:06 ` irq-type-flags.patch Andi Kleen

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=20051109152659.GD27540@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=akpm@osdl.org \
    --cc=lethal@linux-sh.org \
    --cc=linux-arch@vger.kernel.org \
    /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.