All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Davidlohr Bueso <davidlohr@hp.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	"Paul E. McKenney" <paulmck@us.ibm.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] locking tree changes for v3.16
Date: Thu, 5 Jun 2014 14:53:21 +0200	[thread overview]
Message-ID: <20140605125321.GG6758@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20140605111110.GA26771@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]

On Thu, Jun 05, 2014 at 01:11:10PM +0200, Ingo Molnar wrote:
> Unfortunately even with the latest bits from you the breakage I 
> reported weeks ago is not resolved:
> 
> In file included from include/linux/spinlock_types.h:15:0,
>                  from kernel/bounds.c:14:
> include/linux/spinlock_types_up.h:19:3: error: conflicting types for ‘arch_spinlock_t’
> In file included from /home/mingo/linux/linux2/arch/x86/include/asm/paravirt_types.h:329:0,
>                  from /home/mingo/linux/linux2/arch/x86/include/asm/ptrace.h:64,
>                  from /home/mingo/linux/linux2/arch/x86/include/asm/alternative.h:8,
>                  from /home/mingo/linux/linux2/arch/x86/include/asm/bitops.h:16,
>                  from include/linux/bitops.h:33,
>                  from include/linux/kernel.h:10,
>                  from include/asm-generic/bug.h:13,
>                  from /home/mingo/linux/linux2/arch/x86/include/asm/bug.h:35,
>                  from include/linux/bug.h:4,
>                  from include/linux/page-flags.h:9,
>                  from kernel/bounds.c:9:

OK, That's UP + paravirt. The one I fixed a few weeks ago was SMP +
paravirt.

Lemme go kick some headers.

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2014-06-05 12:53 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-03 11:48 [GIT PULL] locking tree changes for v3.16 Ingo Molnar
2014-06-03 21:50 ` Davidlohr Bueso
2014-06-03 21:55   ` Andrew Morton
2014-06-03 22:02     ` Davidlohr Bueso
2014-06-03 22:53       ` Andrew Morton
2014-06-04 10:30   ` Peter Zijlstra
2014-06-04 16:17     ` Linus Torvalds
2014-06-04 17:22       ` Peter Zijlstra
2014-06-04 21:22         ` Linus Torvalds
2014-06-04 21:35           ` Thomas Gleixner
2014-06-05  1:22           ` Davidlohr Bueso
2014-06-05  8:19           ` Ingo Molnar
2014-06-05  8:22             ` Thomas Gleixner
2014-06-05  8:29               ` Ingo Molnar
2014-06-05  8:17     ` Ingo Molnar
2014-06-05  9:21       ` Peter Zijlstra
2014-06-05  9:24         ` Ingo Molnar
2014-06-05 11:11       ` Ingo Molnar
2014-06-05 11:20         ` Ingo Molnar
2014-06-05 12:27         ` Peter Zijlstra
2014-06-05 12:35           ` Ingo Molnar
2014-06-05 12:41             ` Peter Zijlstra
2014-06-05 12:47               ` Ingo Molnar
2014-06-05 12:53         ` Peter Zijlstra [this message]
2014-06-05 13:13           ` Peter Zijlstra

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140605125321.GG6758@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=davidlohr@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=paulmck@us.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.