DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.de;
  h=Received:X-YMail-OSG:Received:Date:From:To:Cc:Subject:Message-ID:Reply-To:MIME-Version:Content-Type:Content-Disposition:Content-Transfer-Encoding:User-Agent;
  b=z31IxTX4pd9gBtyjfDKS3a7sO+9IEGWW6IpwqQcq6ux7ueqt8+n0hUynOPg9F0uQedWjUwb/6xjjYiVWuVCK+NQFkrcBvLMQOCEPuExyktuRKp+gswLz/wX1SxIVcmf5VO1vIV3DE5hfvuN80yQcBK0pop4MUTyC30sq8fGFnDU=  ;
Date: Sat, 12 May 2007 20:07:04 +0200
From: Borislav Petkov <bbpetkov@yahoo.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Scheduled removal of SA_xxx interrupt flags
Message-ID: <20070512180703.GA22918@gollum.tnic>
Reply-To: bbpetkov@yahoo.de
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.5.13 (2006-08-11)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 857
Lines: 19

Hi Andrew,

   i've been going over the interrupt-handling code and noticed that the SA_xxx
   interrupt flags are scheduled for removal sometime in 9/2007 with a prior
   grace period of 6 months for people to fix external stuff. In order to do so,
   a __deprecated inline function wraps those flags.
   What puzzles me is that the __deprecated-patches are only in -mm and not in
   mainline. Is the -mm-testing audience wide enough to cause userspace to fix
   their apps prior to the SA_xxx removal or am I missing something? I.e,
   shouldn't tglx's patches hit mainline first?

-- 
Regards/Gru?,
    Boris.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/