linux-kernel - Re: [2.6 patch] feature-removal-schedule: remove SA

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 25 Oct 2007 11:28:55 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Adrian Bunk <bunk@...nel.org>
cc:	"Ahmed S. Darwish" <darwish.07@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [2.6 patch] feature-removal-schedule: remove SA_* flags entry



On Wed, 24 Oct 2007, Adrian Bunk wrote:

> No reason to keep the feature-removal-schedule.txt entry after the code
> was removed.
> 
> Signed-off-by: Adrian Bunk <bunk@...nel.org>

Acked-by: Thomas Gleixner <tglx@...utronix.de>

> ---
> 
>  Documentation/feature-removal-schedule.txt |    9 ---------
>  1 file changed, 9 deletions(-)
> 
> ecf4ac4330ec61cecb1665c8c39702e600633b80 
> diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
> index 6b0f963..b9b8269 100644
> --- a/Documentation/feature-removal-schedule.txt
> +++ b/Documentation/feature-removal-schedule.txt
> @@ -191,15 +191,6 @@ Who:	Nick Piggin <npiggin@...e.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@...utronix.de>
> -
> ----------------------------
> -
>  What:	PHYSDEVPATH, PHYSDEVBUS, PHYSDEVDRIVER in the uevent environment
>  When:	October 2008
>  Why:	The stacking of class devices makes these values misleading and
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/