From: Jens Axboe <axboe@kernel.dk>
To: 国炬方 <fangguoju@gmail.com>
Cc: Coly Li <colyli@suse.de>,
linux-bcache@vger.kernel.org, linux-block@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 1/1] bcache: add separate workqueue for journal_write to avoid deadlock
Date: Thu, 27 Sep 2018 10:06:35 -0600 [thread overview]
Message-ID: <20fee655-d18d-c931-a910-f8965bda71e0@kernel.dk> (raw)
In-Reply-To: <CAB1iPWn1kYVDMdSFJC6BgzKRP781ijzW5c-m93LsQuzQofeOTQ@mail.gmail.com>
On 9/27/18 9:57 AM, 国炬方 wrote:
> Yes, Guoju Fang. Thx. :)
OK, I made that change and committed it. Just be sure to use your full
name in the future for signoffs, etc.
--
Jens Axboe
prev parent reply other threads:[~2018-09-27 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180927154146.28262-1-colyli@suse.de>
2018-09-27 15:41 ` [PATCH 1/1] bcache: add separate workqueue for journal_write to avoid deadlock Coly Li
2018-09-27 15:46 ` Jens Axboe
[not found] ` <CAB1iPWn1kYVDMdSFJC6BgzKRP781ijzW5c-m93LsQuzQofeOTQ@mail.gmail.com>
2018-09-27 16:06 ` Jens Axboe [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=20fee655-d18d-c931-a910-f8965bda71e0@kernel.dk \
--to=axboe@kernel.dk \
--cc=colyli@suse.de \
--cc=fangguoju@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=stable@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 NNTP newsgroup(s).