public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: David Miller <davem@davemloft.net>
Cc: rmk+lkml@arm.linux.org.uk, mingo@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: SA_TRIGGER_* vs. SA_SAMPLE_RANDOM
Date: Fri, 30 Jun 2006 22:27:27 +0200	[thread overview]
Message-ID: <1151699247.25491.806.camel@localhost.localdomain> (raw)
In-Reply-To: <20060630.132128.26278530.davem@davemloft.net>

On Fri, 2006-06-30 at 13:21 -0700, David Miller wrote:
> From: Russell King <rmk+lkml@arm.linux.org.uk>
> Date: Fri, 30 Jun 2006 19:47:45 +0100
> 
> > On Fri, Jun 30, 2006 at 04:00:07PM +0200, Thomas Gleixner wrote:
> > > We have the same hassle with SA_INTERRUPT. The question arises, if we
> > > should move the SA_XX flags for interrupts completely out of the signal
> > > SA name space. Rename to IRQ_xxx and put them into interrupt.h.
> > 
> > It would probably be sensible, but isn't there rather a lot of
> > drivers to update?  We could do it as a transitional thing -
> > #define the old SA_* names to the new in interrupt.h for a while.
> 
> This seems like a sane plan.
> 
> Someone skilled in sed and awk could probably do the whole
> current tree up in a short amount of time though :-)
> 
> I would then only keep the existing defines around for the
> sake of being polite to out-of-tree folks :)  Put them in
> the deprecation schedule, then zap them for good a few months
> from now.

I'll cook it up tomorrow.

	tglx



  reply	other threads:[~2006-06-30 20:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-29 21:17 SA_TRIGGER_* vs. SA_SAMPLE_RANDOM David Miller
2006-06-30 14:00 ` Thomas Gleixner
2006-06-30 18:47   ` Russell King
2006-06-30 20:21     ` David Miller
2006-06-30 20:27       ` Thomas Gleixner [this message]
2006-06-30 20:31         ` David Miller
2006-06-30 22:25           ` Thomas Gleixner
2006-07-01  0:14             ` Benjamin Herrenschmidt
2006-07-01  0:10   ` Benjamin Herrenschmidt

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=1151699247.25491.806.camel@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rmk+lkml@arm.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