From: Peter Rosin <peda@axentia.se>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Wolfram Sang <wsa@the-dreams.de>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will.deacon@arm.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Philippe Ombredanne <pombredanne@nexb.com>,
Thomas Gleixner <tglx@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-i2c@vger.kernel.org, Peter Chang <dpf@google.com>,
Deepa Dinamani <deepadinamani@google.com>,
John Sperbeck <jsperbeck@google.com>
Subject: Re: [PATCH v4 1/2] rtmutex: allow specifying a subclass for nested locking
Date: Tue, 11 Sep 2018 02:58:52 +0200 [thread overview]
Message-ID: <e85878a5-a5ae-59ea-0101-20361f49d32d@axentia.se> (raw)
In-Reply-To: <20180910232712.fcpdfaagm4xdb24n@home.goodmis.org>
On 2018-09-11 01:27, Steven Rostedt wrote:
>
> Why this:
>
> #ifdef CONFIG_DEBUG_LOCK_ALLOC
> [..]
> #endif
>
> #ifndef CONFIG_DEBUG_LOCK_ALLOC
> [..]
> #endif
>
> ???
>
> This should use #else.
Yes. Water under the bridge...
Cheers,
Peter
next prev parent reply other threads:[~2018-09-11 0:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 8:39 [PATCH v4 0/2] Fix lockdep warning with nested instances of i2c-mux Peter Rosin
2018-07-20 8:39 ` [PATCH v4 1/2] rtmutex: allow specifying a subclass for nested locking Peter Rosin
2018-07-25 14:18 ` [tip:locking/urgent] locking/rtmutex: Allow " tip-bot for Peter Rosin
2018-09-10 23:27 ` [PATCH v4 1/2] rtmutex: allow " Steven Rostedt
2018-09-11 0:58 ` Peter Rosin [this message]
2018-07-20 8:39 ` [PATCH v4 2/2] i2c: mux: annotate the nested rt_mutex usage Peter Rosin
2018-07-25 14:19 ` [tip:locking/urgent] i2c/mux, locking/core: Annotate " tip-bot for Peter Rosin
2018-07-30 16:09 ` Peter Rosin
2018-07-30 17:17 ` 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=e85878a5-a5ae-59ea-0101-20361f49d32d@axentia.se \
--to=peda@axentia.se \
--cc=dave@stgolabs.net \
--cc=deepadinamani@google.com \
--cc=dpf@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jsperbeck@google.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pombredanne@nexb.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
--cc=wsa@the-dreams.de \
/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.