From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Robert P. J. Day" <rpjday@mindspring.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RFC] Remove final vestiges of interrupt-related "SA_" flags.
Date: Mon, 14 May 2007 12:06:12 -0700 [thread overview]
Message-ID: <4648B324.2030801@goop.org> (raw)
In-Reply-To: <1179169434.7074.9.camel@chaos>
Thomas Gleixner wrote:
> On Mon, 2007-05-14 at 14:38 -0400, Robert P. J. Day wrote:
>
>> diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
>> index 498ff31..c5d7775 100644
>> --- a/Documentation/feature-removal-schedule.txt
>> +++ b/Documentation/feature-removal-schedule.txt
>> @@ -160,15 +160,6 @@ Who: Greg Kroah-Hartman <gregkh@suse.de>
>>
>> ---------------------------
>>
>> -What: Interrupt only SA_* flags
>> -When: September 2007
>> -Why: The interrupt related SA_* flags are replaced by IRQF_* to move them
>> - out of the signal namespace.
>> -
>> -Who: Thomas Gleixner <tglx@linutronix.de>
>> -
>>
>
> NAK, the removal date is September 2007 so out of tree folks have some
> time to fix their crap.
This might be a good example of targeting a specific kernel version
rather than a date, since anyone who can't fix this immediately with a
simple search'n'replace is probably trying to support multiple kernels,
and knowing that "2.6.24" (or whatever) is the cut-off version is more
useful than "whatever kernel is current in Sept 2007".
J
next prev parent reply other threads:[~2007-05-14 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 18:38 [PATCH][RFC] Remove final vestiges of interrupt-related "SA_" flags Robert P. J. Day
2007-05-14 19:03 ` Thomas Gleixner
2007-05-14 19:06 ` Jeremy Fitzhardinge [this message]
2007-05-14 19:16 ` Russell King
2007-05-14 19:18 ` Thomas Gleixner
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=4648B324.2030801@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
--cc=tglx@linutronix.de \
/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.