From: Kent Overstreet <kent.overstreet@linux.dev>
To: linux-bcache@vger.kernel.org, linux-bcachefs@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Kent Overstreet <kent.overstreet@linux.dev>
Subject: [PATCH 0/2] Two small closures patches
Date: Tue, 31 Oct 2023 12:24:50 -0400 [thread overview]
Message-ID: <20231031162454.3761482-1-kent.overstreet@linux.dev> (raw)
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(-)
--
2.42.0
next reply other threads:[~2023-10-31 16:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 16:24 Kent Overstreet [this message]
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
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=20231031162454.3761482-1-kent.overstreet@linux.dev \
--to=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