> But whatever works. I'm currently skipping the patches since they didn't > seem like 2.6.24 fodder anyway. The vdso cleanups are pure cleanup, not fixing anything that's actively broken. Thanks, Roland - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- [PATCH 00/18] x86 vDSO revamp
- From: Roland McGrath <[email protected]>
- [PATCH 06/18] x86 vDSO: arch/x86/vdso/vdso32
- From: Roland McGrath <[email protected]>
- Re: [PATCH 06/18] x86 vDSO: arch/x86/vdso/vdso32
- From: Thomas Gleixner <[email protected]>
- Re: [PATCH 06/18] x86 vDSO: arch/x86/vdso/vdso32
- From: Roland McGrath <[email protected]>
- Re: [PATCH 06/18] x86 vDSO: arch/x86/vdso/vdso32
- From: Thomas Gleixner <[email protected]>
- Re: [PATCH 06/18] x86 vDSO: arch/x86/vdso/vdso32
- From: Roland McGrath <[email protected]>
- Re: [PATCH 06/18] x86 vDSO: arch/x86/vdso/vdso32
- From: Linus Torvalds <[email protected]>
- [PATCH 00/18] x86 vDSO revamp
- Prev by Date: Re: [PATCH 06/18] x86 vDSO: arch/x86/vdso/vdso32
- Next by Date: Re: [PATCHv4 5/6] Allow setting O_NONBLOCK flag for new sockets
- Previous by thread: Re: [PATCH 06/18] x86 vDSO: arch/x86/vdso/vdso32
- Next by thread: [PATCH 07/18] x86 vDSO: vdso32 build
- Index(es):