On Friday 06 January 2006 12:22, you wrote: > On Fri, 2006-01-06 at 12:18 +0100, Michael Buesch wrote: > > On Friday 06 January 2006 11:42, you wrote: > > > Index: linux-2.6.15/include/linux/sched.h > > > =================================================================== > > > --- linux-2.6.15.orig/include/linux/sched.h > > > +++ linux-2.6.15/include/linux/sched.h > > > @@ -1102,19 +1102,8 @@ static inline int sas_ss_flags(unsigned > > > } > > > > > > > > > -#ifdef CONFIG_SECURITY > > > -/* code is in security.c */ > > > +/* code is in security.c or kernel/sys.c if !SECURITY */ > > > extern int capable(int cap); > > > > BTW, is there a special reason why this is declared in sched.h > > instead of capability.h? > > probably a lot of historic bagage... anyway not something that should be > cleaned up as part of this series, could maybe be done in another patch > if you feel so inclined :) Oh, well I have more important work to do now. :) I am sure there are enough people around on this mailing list waiting for such work... hint hint :) -- Greetings Michael.
Attachment:
pgpQ0ByKk5hPL.pgp
Description: PGP signature
- Follow-Ups:
- [PATCH 1/4] move capable() to capability.h
- From: "Randy.Dunlap" <[email protected]>
- [PATCH 1/4] move capable() to capability.h
- References:
- [patch 1/7] Make __always_inline actually force always inlining
- From: Arjan van de Ven <[email protected]>
- Re: [patch 5/7] uninline capable()
- From: Michael Buesch <[email protected]>
- Re: [patch 5/7] uninline capable()
- From: Arjan van de Ven <[email protected]>
- [patch 1/7] Make __always_inline actually force always inlining
- Prev by Date: Re: [patch 5/7] uninline capable()
- Next by Date: Re: State of the Union: Wireless
- Previous by thread: Re: [patch 5/7] uninline capable()
- Next by thread: [PATCH 1/4] move capable() to capability.h
- Index(es):
 |