feature-removal-schedule: remove SA_* flags entry
PATCH 1/1 feature-removal-schedule: remove SA_* flags entry
No reason to keep the feature-removal-schedule.txt entry after the code was removed.
Signed-off-by Adrian Bunk <[email protected]>
---
Documentation/feature-removal-schedule.txt | 9 --------- 1 file changed, 9 deletions(-)
ecf4ac4330ec61cecb1665c8c39702e600633b80
Documentation/feature-removal-schedule.txt +0 -9
@@ -191,15 +191,6 @@ Who: Nick Piggin <[email protected]> --------------------------- -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 <[email protected]> - ---------------------------- - What: PHYSDEVPATH, PHYSDEVBUS, PHYSDEVDRIVER in the uevent environment When: October 2008 Why: The stacking of class devices makes these values misleading and
Quoted 4 lines · Adrian Bunk
No reason to keep the feature-removal-schedule.txt entry after the code was removed.
Signed-off-by Adrian Bunk <[email protected]>
Acked-by Thomas Gleixner <[email protected]>
Quoted 27 lines
---
Documentation/feature-removal-schedule.txt | 9 --------- 1 file changed, 9 deletions(-)
ecf4ac4330ec61cecb1665c8c39702e600633b80Documentation/feature-removal-schedule.txt +0
-9@@ -191,15 +191,6 @@ Who: Nick Piggin <[email protected]> --------------------------- -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 <[email protected]> - ---------------------------- - What: PHYSDEVPATH, PHYSDEVBUS, PHYSDEVDRIVER in the uevent environment When: October 2008 Why: The stacking of class devices makes these values misleading and