From: Mark Brown <broonie@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] mutex: make mutex_lock_nested an inline function
Date: Wed, 14 Oct 2015 10:59:51 +0100 [thread overview]
Message-ID: <20151014095950.GQ14956@sirena.org.uk> (raw)
In-Reply-To: <20151014090815.GS17308@twins.programming.kicks-ass.net>
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
On Wed, Oct 14, 2015 at 11:08:15AM +0200, Peter Zijlstra wrote:
> On Wed, Oct 14, 2015 at 11:00:20AM +0200, Arnd Bergmann wrote:
> > On Wednesday 14 October 2015 10:37:07 Peter Zijlstra wrote:
> > but apparently this is work-in-progress and the plan is to use it
> > in 4.4 when the rest of the currently-under-review patches are merged.
> And here I thought we had a fairly strong rule that we should not merge
> unused code :/
The revisions are very minor (and are sitting in my inbox for me to
look at just now), and keeping things out of tree just makes it more
difficult to get them merged - it's one thing if things are getting in
the way for a long time or have a high cost but that's not the case
here.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-10-14 10:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 20:30 Arnd Bergmann
2015-10-13 20:38 ` Peter Zijlstra
2015-10-13 21:46 ` Arnd Bergmann
2015-10-14 8:20 ` Peter Zijlstra
2015-10-14 8:37 ` Peter Zijlstra
2015-10-14 9:00 ` Arnd Bergmann
2015-10-14 9:08 ` Peter Zijlstra
2015-10-14 9:59 ` Mark Brown [this message]
2015-10-14 10:27 ` Mark Brown
2015-10-14 11:07 ` Peter Zijlstra
2015-10-14 12:36 ` Mark Brown
2015-10-14 13:47 ` Peter Zijlstra
2015-10-14 13:50 ` Peter Zijlstra
2015-10-14 13:58 ` Ingo Molnar
2015-10-14 14:11 ` Mark Brown
2015-10-22 15:02 ` Arnd Bergmann
2015-10-22 15:09 ` Peter Zijlstra
2015-10-22 17:44 ` Russell King - ARM Linux
2015-10-27 18:13 ` Ingo Molnar
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=20151014095950.GQ14956@sirena.org.uk \
--to=broonie@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®