public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>, Ingo Molnar <mingo@elte.hu>
Subject: [patch 01/18] genirq: prepare removal of obsolete defines and typedefs
Date: Wed, 11 Mar 2009 00:45:24 -0000	[thread overview]
Message-ID: <20090311003235.403132610@linutronix.de> (raw)
In-Reply-To: 20090311003204.592133594@linutronix.de

[-- Attachment #1: genirq-prepare-removal-of-obsolete-defines-and-typedefs.patch --]
[-- Type: text/plain, Size: 987 bytes --]

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
---
 Documentation/feature-removal-schedule.txt |    9 +++++++++
 1 file changed, 9 insertions(+)

Index: linux-2.6/Documentation/feature-removal-schedule.txt
===================================================================
--- linux-2.6.orig/Documentation/feature-removal-schedule.txt
+++ linux-2.6/Documentation/feature-removal-schedule.txt
@@ -344,3 +344,12 @@ Why:	See commits 129f8ae9b1b5be94517da76
 	Removal is subject to fixing any remaining bugs in ACPI which may
 	cause the thermal throttling not to happen at the right time.
 Who:	Dave Jones <davej@redhat.com>, Matthew Garrett <mjg@redhat.com>
+
+---------------------------
+
+What:	obsolete generic irq defines and typedefs
+When:	2.6.30
+Why:	The defines and typedefs (hw_interrupt_type, no_irq_type, irq_desc_t)
+	have been kept around for migration reasons. After more than two years
+	it's time to remove them finally
+Who:	Thomas Gleixner <tglx@linutronix.de>



  reply	other threads:[~2009-03-11  0:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-11  0:45 [patch 00/18] Remove obsolete genirq defines and typedefs Thomas Gleixner
2009-03-11  0:45 ` Thomas Gleixner [this message]
2009-03-11  0:45 ` [patch 02/18] ia64: convert obsolete no_irq_type to no_irq_chip Thomas Gleixner
2009-03-11  0:45 ` [patch 03/18] mn10300: " Thomas Gleixner
2009-03-11 11:35   ` David Howells
2009-03-11  0:45 ` [patch 04/18] sh: " Thomas Gleixner
2009-03-11  0:45 ` [patch 05/18] ia64: convert obsolete irq_desc_t to struct irq_desc Thomas Gleixner
2009-03-11  0:45 ` [patch 06/18] drivers/mfd: " Thomas Gleixner
2009-03-11  0:45 ` [patch 07/18] mips: " Thomas Gleixner
2009-03-11 16:00   ` David Daney
2009-03-11 17:31   ` Ralf Baechle
2009-03-11  0:45 ` [patch 08/18] powerpc: " Thomas Gleixner
2009-03-11  2:19   ` Benjamin Herrenschmidt
2009-03-11  7:59     ` Thomas Gleixner
2009-03-11  0:45 ` [patch 09/18] x86: " Thomas Gleixner
2009-03-11  0:46 ` [patch 10/18] alpha: convert obsolete hw_interrupt_type to struct irq_chip Thomas Gleixner
2009-03-11  0:46 ` [patch 11/18] avr32: " Thomas Gleixner
2009-03-11  0:46 ` [patch 12/18] cris: " Thomas Gleixner
2009-04-02 12:31   ` Jesper Nilsson
2009-03-11  0:46 ` [patch 13/18] ia64: " Thomas Gleixner
2009-03-11  0:46 ` [patch 14/18] m32r: " Thomas Gleixner
2009-03-11  0:46 ` [patch 15/18] parisc: " Thomas Gleixner
2009-03-11  0:46 ` [patch 16/18] powerpc: " Thomas Gleixner
2009-03-11  2:19   ` Benjamin Herrenschmidt
2009-03-11  0:46 ` [patch 17/18] sh: " Thomas Gleixner
2009-03-11  0:46 ` [patch 18/18] um: " 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=20090311003235.403132610@linutronix.de \
    --to=tglx@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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