From: Ingo Molnar <mingo@kernel.org>
To: Maarten Lankhorst <maarten.lankhorst@canonical.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Dave Airlie <airlied@gmail.com>
Subject: Re: [GIT PULL] core/mutexes changes for v3.11: W/W mutex support
Date: Fri, 5 Jul 2013 08:23:45 +0200 [thread overview]
Message-ID: <20130705062345.GA29487@gmail.com> (raw)
In-Reply-To: <51D3C4C8.8060701@canonical.com>
* Maarten Lankhorst <maarten.lankhorst@canonical.com> wrote:
> Hey,
>
> Op 03-07-13 02:54, Linus Torvalds schreef:
> > On Mon, Jul 1, 2013 at 1:22 AM, Ingo Molnar <mingo@kernel.org> wrote:
> >> Please pull the latest core-mutexes-for-linus git tree from:
> >>
> >> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core-mutexes-for-linus
> >>
> >> HEAD: 166989e366ffa66108b2f37b870e66b85b2185ad locking-selftests: Handle unexpected failures more strictly
> >>
> >> This tree adds support for wound/wait style locks, which the graphics guys
> >> would like to make use of in the TTM graphics subsystem.
> > So I pulled this, but I'm not particularly happy with how this (very
> > unusual) lock pollutes <linux/mutex.h> that pretty much every single
> > file ends up including.
> >
> > So I'd really prefer to see the ww_mutex() support split up into
> > <linux/ww_mutex.h>, rather than making the compiler have to parse and
> > remember that stuff when 99.99% of all files do not care about it or
> > need it.
>
> Sounds good to me, but can it wait until with the drm pull is done?
The ordering should not matter much as the combination will be tested in
linux-next anyway.
> Preliminary diff below.
Looks good to me at first sight. Please send a tested, changelogged,
signed off version.
Thanks,
Ingo
next prev parent reply other threads:[~2013-07-05 6:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 8:22 [GIT PULL] core/mutexes changes for v3.11: W/W mutex support Ingo Molnar
2013-07-03 0:54 ` Linus Torvalds
2013-07-03 6:29 ` Maarten Lankhorst
2013-07-05 6:23 ` Ingo Molnar [this message]
2013-07-05 7:29 ` [PATCH] mutex: move ww_mutex definitions to ww_mutex.h Maarten Lankhorst
2013-07-12 13:28 ` [tip:core/locking] mutex: Move " tip-bot for Maarten Lankhorst
2013-07-30 8:13 ` [PATCH] mutex: fix deadlock injection Maarten Lankhorst
2013-07-30 8:41 ` Peter Zijlstra
2013-08-07 0:05 ` Dave Airlie
2013-08-07 6:22 ` Maarten Lankhorst
2013-07-30 13:09 ` Alex Deucher
2013-07-31 8:55 ` [tip:core/urgent] mutex: Fix w/w mutex " tip-bot for Maarten Lankhorst
2013-08-05 7:58 ` [PATCH] mutex: fix " Daniel Vetter
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=20130705062345.GA29487@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@canonical.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).