All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Peter Rosin <peda@axentia.se>
Cc: tglx@linutronix.de, jsperbeck@google.com,
	linux-kernel@vger.kernel.org, wsa@the-dreams.de,
	dave@stgolabs.net, dpf@google.com, pombredanne@nexb.com,
	deepadinamani@google.com, peterz@infradead.org,
	gregkh@linuxfoundation.org, will.deacon@arm.com,
	torvalds@linux-foundation.org, hpa@zytor.com,
	linux-tip-commits@vger.kernel.org
Subject: Re: [tip:locking/urgent] i2c/mux, locking/core: Annotate the nested rt_mutex usage
Date: Mon, 30 Jul 2018 19:17:23 +0200	[thread overview]
Message-ID: <20180730171723.GA31541@gmail.com> (raw)
In-Reply-To: <0bb2d26f-3d1a-fcb8-8fc4-9123a2d5a30d@axentia.se>


* Peter Rosin <peda@axentia.se> wrote:

> On 2018-07-25 16:19, tip-bot for Peter Rosin wrote:
> > Commit-ID:  7b94ea50514d1a0dc94f02723b603c27bc0ea597
> > Gitweb:     https://git.kernel.org/tip/7b94ea50514d1a0dc94f02723b603c27bc0ea597
> > Author:     Peter Rosin <peda@axentia.se>
> > AuthorDate: Fri, 20 Jul 2018 10:39:14 +0200
> > Committer:  Ingo Molnar <mingo@kernel.org>
> > CommitDate: Wed, 25 Jul 2018 11:22:20 +0200
> > 
> > i2c/mux, locking/core: Annotate the nested rt_mutex usage
> 
> Hi!
> 
> I'm a bit curious as to why the subject line was changed on this patch?
> 
> (it was "[PATCH v4 2/2] i2c: mux: annotate the nested rt_mutex usage")
> 
> I thought the subject as I wrote it was just perfect. Was it so bad that it
> had to be edited?

It wasn't "bad", I improved it to signal that it has a new locking API dependency,
in particular that's it's dependent on this commit:

  62cedf3e60af: locking/rtmutex: Allow specifying a subclass for nested locking

This also clarified it why this i2c commit is in locking/urgent.

Thanks,

	Ingo

      reply	other threads:[~2018-07-30 17:17 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
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 [this message]

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=20180730171723.GA31541@gmail.com \
    --to=mingo@kernel.org \
    --cc=dave@stgolabs.net \
    --cc=deepadinamani@google.com \
    --cc=dpf@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=jsperbeck@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=peda@axentia.se \
    --cc=peterz@infradead.org \
    --cc=pombredanne@nexb.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --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.