Re: [tip:x86/vdso] x86, vdso: Instead of dummy functions, include < linux/spinlock_up.h>

2014-02-17 Thread Stefani Seibold
Am Montag, den 17.02.2014, 01:50 -0800 schrieb H. Peter Anvin: > On 02/17/2014 01:46 AM, Stefani Seibold wrote: > > Am Montag, den 17.02.2014, 01:27 -0800 schrieb H. Peter Anvin: > >> On 02/16/2014 11:42 PM, Stefani Seibold wrote: > >>> I think for the first time it will be okay to kick out the >

Re: [tip:x86/vdso] x86, vdso: Instead of dummy functions, include < linux/spinlock_up.h>

2014-02-17 Thread H. Peter Anvin
On 02/17/2014 01:46 AM, Stefani Seibold wrote: Am Montag, den 17.02.2014, 01:27 -0800 schrieb H. Peter Anvin: On 02/16/2014 11:42 PM, Stefani Seibold wrote: I think for the first time it will be okay to kick out the _ASM_X86_SPINLOCK_H hack and accept the C=1 warnings. At next step it is

Re: [tip:x86/vdso] x86, vdso: Instead of dummy functions, include < linux/spinlock_up.h>

2014-02-17 Thread Stefani Seibold
Am Montag, den 17.02.2014, 01:27 -0800 schrieb H. Peter Anvin: > On 02/16/2014 11:42 PM, Stefani Seibold wrote: > > I think for the first time it will be okay to kick out the > > _ASM_X86_SPINLOCK_H hack and accept the C=1 warnings. > > > > At next step it is necessary to make the whole

Re: [tip:x86/vdso] x86, vdso: Instead of dummy functions, include < linux/spinlock_up.h>

2014-02-17 Thread H. Peter Anvin
On 02/16/2014 11:42 PM, Stefani Seibold wrote: I think for the first time it will be okay to kick out the _ASM_X86_SPINLOCK_H hack and accept the C=1 warnings. At next step it is necessary to make the whole BUILD_VDSO32 path in vclock_gettime.c independent from the kernel headers, only uapi/

Re: [tip:x86/vdso] x86, vdso: Instead of dummy functions, include linux/spinlock_up.h

2014-02-17 Thread H. Peter Anvin
On 02/16/2014 11:42 PM, Stefani Seibold wrote: I think for the first time it will be okay to kick out the _ASM_X86_SPINLOCK_H hack and accept the C=1 warnings. At next step it is necessary to make the whole BUILD_VDSO32 path in vclock_gettime.c independent from the kernel headers, only uapi/

Re: [tip:x86/vdso] x86, vdso: Instead of dummy functions, include linux/spinlock_up.h

2014-02-17 Thread Stefani Seibold
Am Montag, den 17.02.2014, 01:27 -0800 schrieb H. Peter Anvin: On 02/16/2014 11:42 PM, Stefani Seibold wrote: I think for the first time it will be okay to kick out the _ASM_X86_SPINLOCK_H hack and accept the C=1 warnings. At next step it is necessary to make the whole BUILD_VDSO32 path

Re: [tip:x86/vdso] x86, vdso: Instead of dummy functions, include linux/spinlock_up.h

2014-02-17 Thread H. Peter Anvin
On 02/17/2014 01:46 AM, Stefani Seibold wrote: Am Montag, den 17.02.2014, 01:27 -0800 schrieb H. Peter Anvin: On 02/16/2014 11:42 PM, Stefani Seibold wrote: I think for the first time it will be okay to kick out the _ASM_X86_SPINLOCK_H hack and accept the C=1 warnings. At next step it is

Re: [tip:x86/vdso] x86, vdso: Instead of dummy functions, include linux/spinlock_up.h

2014-02-17 Thread Stefani Seibold
Am Montag, den 17.02.2014, 01:50 -0800 schrieb H. Peter Anvin: On 02/17/2014 01:46 AM, Stefani Seibold wrote: Am Montag, den 17.02.2014, 01:27 -0800 schrieb H. Peter Anvin: On 02/16/2014 11:42 PM, Stefani Seibold wrote: I think for the first time it will be okay to kick out the

Re: [tip:x86/vdso] x86, vdso: Instead of dummy functions, include < linux/spinlock_up.h>

2014-02-16 Thread Stefani Seibold
Hi Peter, Am Sonntag, den 16.02.2014, 20:06 -0800 schrieb H. Peter Anvin: > On 02/16/2014 07:51 PM, tip-bot for H. Peter Anvin wrote: > > Commit-ID: bd9ee7fd99f127ee1306289415141d45792c97f3 > > Gitweb: > > http://git.kernel.org/tip/bd9ee7fd99f127ee1306289415141d45792c97f3 > > Author: H.

Re: [tip:x86/vdso] x86, vdso: Instead of dummy functions, include < linux/spinlock_up.h>

2014-02-16 Thread H. Peter Anvin
On 02/16/2014 07:51 PM, tip-bot for H. Peter Anvin wrote: > Commit-ID: bd9ee7fd99f127ee1306289415141d45792c97f3 > Gitweb: http://git.kernel.org/tip/bd9ee7fd99f127ee1306289415141d45792c97f3 > Author: H. Peter Anvin > AuthorDate: Sun, 16 Feb 2014 19:47:01 -0800 > Committer: H. Peter Anvin

[tip:x86/vdso] x86, vdso: Instead of dummy functions, include < linux/spinlock_up.h>

2014-02-16 Thread tip-bot for H. Peter Anvin
Commit-ID: bd9ee7fd99f127ee1306289415141d45792c97f3 Gitweb: http://git.kernel.org/tip/bd9ee7fd99f127ee1306289415141d45792c97f3 Author: H. Peter Anvin AuthorDate: Sun, 16 Feb 2014 19:47:01 -0800 Committer: H. Peter Anvin CommitDate: Sun, 16 Feb 2014 19:47:01 -0800 x86, vdso: Instead of

[tip:x86/vdso] x86, vdso: Instead of dummy functions, include linux/spinlock_up.h

2014-02-16 Thread tip-bot for H. Peter Anvin
Commit-ID: bd9ee7fd99f127ee1306289415141d45792c97f3 Gitweb: http://git.kernel.org/tip/bd9ee7fd99f127ee1306289415141d45792c97f3 Author: H. Peter Anvin h...@linux.intel.com AuthorDate: Sun, 16 Feb 2014 19:47:01 -0800 Committer: H. Peter Anvin h...@linux.intel.com CommitDate: Sun, 16 Feb

Re: [tip:x86/vdso] x86, vdso: Instead of dummy functions, include linux/spinlock_up.h

2014-02-16 Thread H. Peter Anvin
On 02/16/2014 07:51 PM, tip-bot for H. Peter Anvin wrote: Commit-ID: bd9ee7fd99f127ee1306289415141d45792c97f3 Gitweb: http://git.kernel.org/tip/bd9ee7fd99f127ee1306289415141d45792c97f3 Author: H. Peter Anvin h...@linux.intel.com AuthorDate: Sun, 16 Feb 2014 19:47:01 -0800 Committer:

Re: [tip:x86/vdso] x86, vdso: Instead of dummy functions, include linux/spinlock_up.h

2014-02-16 Thread Stefani Seibold
Hi Peter, Am Sonntag, den 16.02.2014, 20:06 -0800 schrieb H. Peter Anvin: On 02/16/2014 07:51 PM, tip-bot for H. Peter Anvin wrote: Commit-ID: bd9ee7fd99f127ee1306289415141d45792c97f3 Gitweb: http://git.kernel.org/tip/bd9ee7fd99f127ee1306289415141d45792c97f3 Author: H. Peter