All of lore.kernel.org
 help / color / mirror / Atom feed
From: peterz@infradead.org (Peter Zijlstra)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mutex: make mutex_lock_nested an inline function
Date: Wed, 14 Oct 2015 11:08:15 +0200	[thread overview]
Message-ID: <20151014090815.GS17308@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <11240940.NHO2vFoJOz@wuerfel>

On Wed, Oct 14, 2015 at 11:00:20AM +0200, Arnd Bergmann wrote:
> On Wednesday 14 October 2015 10:37:07 Peter Zijlstra wrote:

> > > Uuh, I just looked at next and saw this regulator_lock_supply()
> > > function. How is that limited? subclass must be <8 otherwise bad things
> > > happen.
> > 
> > Also, the function appears unused, just delete it 
> 
> That was my first suggestion as well when I ran into 
> 
> drivers/regulator/core.c:139:13: warning: 'regulator_lock_supply' defined but not used
> 
> 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 :/

In any case, whomever wrote that function had better first explain why
its not broken.

And I'm not too keen on making mutex_lock_nested() an inline due it
being too easy to generate code with it. I'd much rather work around the
occasional warning than have to deal with silent but unintended code
spills.

WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org,
	Liam Girdwood <lgirdwood@gmail.com>,
	linux-kernel@vger.kernel.org, Mark Brown <broonie@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 11:08:15 +0200	[thread overview]
Message-ID: <20151014090815.GS17308@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <11240940.NHO2vFoJOz@wuerfel>

On Wed, Oct 14, 2015 at 11:00:20AM +0200, Arnd Bergmann wrote:
> On Wednesday 14 October 2015 10:37:07 Peter Zijlstra wrote:

> > > Uuh, I just looked at next and saw this regulator_lock_supply()
> > > function. How is that limited? subclass must be <8 otherwise bad things
> > > happen.
> > 
> > Also, the function appears unused, just delete it 
> 
> That was my first suggestion as well when I ran into 
> 
> drivers/regulator/core.c:139:13: warning: 'regulator_lock_supply' defined but not used
> 
> 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 :/

In any case, whomever wrote that function had better first explain why
its not broken.

And I'm not too keen on making mutex_lock_nested() an inline due it
being too easy to generate code with it. I'd much rather work around the
occasional warning than have to deal with silent but unintended code
spills.

  reply	other threads:[~2015-10-14  9:08 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-13 20:30 [PATCH] mutex: make mutex_lock_nested an inline function Arnd Bergmann
2015-10-13 20:30 ` Arnd Bergmann
2015-10-13 20:38 ` Peter Zijlstra
2015-10-13 20:38   ` Peter Zijlstra
2015-10-13 21:46   ` Arnd Bergmann
2015-10-13 21:46     ` Arnd Bergmann
2015-10-14  8:20     ` Peter Zijlstra
2015-10-14  8:20       ` Peter Zijlstra
2015-10-14  8:37       ` Peter Zijlstra
2015-10-14  8:37         ` Peter Zijlstra
2015-10-14  9:00         ` Arnd Bergmann
2015-10-14  9:00           ` Arnd Bergmann
2015-10-14  9:08           ` Peter Zijlstra [this message]
2015-10-14  9:08             ` Peter Zijlstra
2015-10-14  9:59             ` Mark Brown
2015-10-14  9:59               ` Mark Brown
2015-10-14 10:27       ` Mark Brown
2015-10-14 10:27         ` Mark Brown
2015-10-14 11:07         ` Peter Zijlstra
2015-10-14 11:07           ` Peter Zijlstra
2015-10-14 12:36           ` Mark Brown
2015-10-14 12:36             ` Mark Brown
2015-10-14 13:47             ` Peter Zijlstra
2015-10-14 13:47               ` Peter Zijlstra
2015-10-14 13:50               ` Peter Zijlstra
2015-10-14 13:50                 ` Peter Zijlstra
2015-10-14 13:58                 ` Ingo Molnar
2015-10-14 13:58                   ` Ingo Molnar
2015-10-14 14:11               ` Mark Brown
2015-10-14 14:11                 ` Mark Brown
2015-10-22 15:02     ` Arnd Bergmann
2015-10-22 15:02       ` Arnd Bergmann
2015-10-22 15:09       ` Peter Zijlstra
2015-10-22 15:09         ` Peter Zijlstra
2015-10-22 17:44         ` Russell King - ARM Linux
2015-10-22 17:44           ` Russell King - ARM Linux
2015-10-27 18:13           ` Ingo Molnar
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=20151014090815.GS17308@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=linux-arm-kernel@lists.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 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.