From: Borislav Petkov <bp@alien8.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Waiman Long <Waiman.Long@hp.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: Linux 3.16-rc6
Date: Thu, 24 Jul 2014 18:34:03 +0200 [thread overview]
Message-ID: <20140724163403.GP19239@pd.tnic> (raw)
In-Reply-To: <20140724125814.GX6758@twins.programming.kicks-ass.net>
On Thu, Jul 24, 2014 at 02:58:14PM +0200, Peter Zijlstra wrote:
> Of course we should have made the lockdep change before merging qrwlock,
> and that's entirely my fail, but with qrwlock in these new semantics are
> already a reality.
>
> We could of course disable qrwlock until all such issues are cleared up
> (its the safe option)...
So we leave in the lockdep change and disable qrwlock ontop of
tip/locking/core. Nothing's hurt yet as this whole pile is queued for
3.17 anyway.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-07-24 16:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 4:22 Linux 3.16-rc6 Linus Torvalds
2014-07-23 9:53 ` Borislav Petkov
2014-07-24 0:37 ` Linus Torvalds
2014-07-24 1:53 ` David Rientjes
2014-07-24 6:43 ` Peter Zijlstra
2014-07-24 8:41 ` Borislav Petkov
2014-07-24 12:25 ` Borislav Petkov
2014-07-24 12:58 ` Peter Zijlstra
2014-07-24 16:34 ` Borislav Petkov [this message]
2014-07-24 18:18 ` Linus Torvalds
2014-07-24 18:36 ` Peter Zijlstra
2014-07-24 20:38 ` Waiman Long
2014-07-24 21:45 ` Borislav Petkov
2014-07-25 17:23 ` Waiman Long
2014-07-24 22:06 ` John Stoffel
2014-07-24 22:06 ` John Stoffel
2014-07-25 16:10 ` Peter Zijlstra
2014-07-28 16:37 ` Waiman Long
2014-07-28 16:42 ` 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=20140724163403.GP19239@pd.tnic \
--to=bp@alien8.de \
--cc=Waiman.Long@hp.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--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.