From: Peter Zijlstra <peterz@infradead.org>
To: Coly Li <colyli@suse.de>
Cc: linux-tip-commits@vger.kernel.org,
Kent Overstreet <kent.overstreet@linux.dev>,
LKML <linux-kernel@vger.kernel.org>,
"Coly Li <colyli@suse.de>" <colyli@suse.de>,
x86@kernel.org
Subject: Re: [tip: locking/core] bcache: Convert to lock_cmp_fn
Date: Mon, 22 May 2023 10:34:58 +0200 [thread overview]
Message-ID: <20230522083458.GM83892@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1FBFDA28-6886-4315-A942-88F3542CE244@suse.de>
On Sun, May 21, 2023 at 09:21:36PM +0800, Coly Li wrote:
>
>
> > 2023年5月20日 18:49,tip-bot2 for Kent Overstreet <tip-bot2@linutronix.de> 写道:
> >
> > The following commit has been merged into the locking/core branch of tip:
> >
> > Commit-ID: 0ad397b556936a14052aa65d8fa958a9f3175add
> > Gitweb: https://git.kernel.org/tip/0ad397b556936a14052aa65d8fa958a9f3175add
> > Author: Kent Overstreet <kent.overstreet@linux.dev>
> > AuthorDate: Tue, 09 May 2023 15:58:47 -04:00
> > Committer: Peter Zijlstra <peterz@infradead.org>
> > CommitterDate: Fri, 19 May 2023 12:35:10 +02:00
> >
> > bcache: Convert to lock_cmp_fn
> >
> > Replace one of bcache's lockdep_set_novalidate_class() usage with the
> > newly introduced custom lock nesting annotation.
> >
> > [peterz: changelog]
> > Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
> > Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> > Acked-by: Coly Li <colyli@suse.de <mailto:colyli@suse.de>>
>
>
> Can the above “<mailto:colyli@suse.de>” be removed from my acked-by. This was automatically and invisibly added by MacOS email client, which just introduced chaos in such use case.
>
> Thanks.
Urgh, something I should add to my script on a rainy day I suppose.
I'll have to rebase the tree, but I suppose I can do that. Let me go see
if I can remember the git incantations required.
next prev parent reply other threads:[~2023-05-22 8:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 19:58 [PATCH 1/2] lockdep: lock_set_cmp_fn() Kent Overstreet
2023-05-09 19:58 ` [PATCH 2/2] bcache: Convert to lock_cmp_fn Kent Overstreet
2023-05-10 5:25 ` Coly Li
2023-05-10 13:01 ` Peter Zijlstra
2023-05-10 17:05 ` Kent Overstreet
2023-05-25 5:07 ` Kent Overstreet
[not found] ` <168457974565.404.16611061652498882569.tip-bot2@tip-bot2>
2023-05-21 13:21 ` [tip: locking/core] " Coly Li
2023-05-22 8:34 ` Peter Zijlstra [this message]
2023-05-24 10:31 ` tip-bot2 for Kent Overstreet
2023-05-09 21:54 ` [PATCH 1/2] lockdep: lock_set_cmp_fn() kernel test robot
2023-05-09 23:26 ` kernel test robot
2023-05-20 10:49 ` [tip: locking/core] lockdep: Add lock_set_cmp_fn() annotation tip-bot2 for Kent Overstreet
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=20230522083458.GM83892@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=colyli@suse.de \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=x86@kernel.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®