From: Coly Li <colyli@suse.de>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: Bcache Linux <linux-bcache@vger.kernel.org>,
linux-bcachefs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Two small closures patches
Date: Sun, 19 Nov 2023 01:20:22 +0800 [thread overview]
Message-ID: <DD7F284F-7133-46A1-A866-31E17604314F@suse.de> (raw)
In-Reply-To: <79FE1457-FC6D-46A9-A7F9-55ADCCBE42DF@suse.de>
> 2023年11月19日 00:43，Coly Li <colyli@suse.de> 写道：
>
>
>
>> 2023年11月1日 00:24，Kent Overstreet <kent.overstreet@linux.dev> 写道：
>>
>> I'll be sending these to Linus in my next pull request, sending them to
>> linux-bcache so Coly gets a chance to see them.
>>
>> Kent Overstreet (2):
>> closures: Better memory barriers
>> closures: Fix race in closure_sync()
>>
>> fs/bcachefs/fs-io-direct.c | 1 +
>> include/linux/closure.h | 12 +++++++++---
>> lib/closure.c | 9 +++++++--
>> 3 files changed, 17 insertions(+), 5 deletions(-)
>
> The whole series got tested with current bcache code, it works fine.
>
> Acked-by: Coly Li <colyli@suse.de <mailto:colyli@suse.de>>
The above line was automatically modified by the MacOS Mail client, sigh…
Please use the following line,
Acked-by: Coly Li <colyli@suse.de>
Thanks.
Coly Li
prev parent reply other threads:[~2023-11-18 17:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 16:24 [PATCH 0/2] Two small closures patches Kent Overstreet
2023-10-31 16:24 ` [PATCH 1/2] closures: Better memory barriers Kent Overstreet
2023-10-31 16:24 ` [PATCH 2/2] closures: Fix race in closure_sync() Kent Overstreet
2023-11-18 16:43 ` [PATCH 0/2] Two small closures patches Coly Li
2023-11-18 17:20 ` Coly Li [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=DD7F284F-7133-46A1-A866-31E17604314F@suse.de \
--to=colyli@suse.de \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).