From: Christoph Hellwig <hch@lst.de>
To: Bart Van Assche <bart.vanassche@wdc.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v2 2/3] block: Document scheduler modification locking requirements
Date: Thu, 18 Jan 2018 17:27:45 +0100 [thread overview]
Message-ID: <20180118162745.GC26078@lst.de> (raw)
In-Reply-To: <20180117194810.26583-3-bart.vanassche@wdc.com>
Looks fine,
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2018-01-18 16:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 19:48 [PATCH v2 0/3] Avoid that blk_{un,}register_queue() trigger lock inversion Bart Van Assche
2018-01-17 19:48 ` [PATCH v2 1/3] block: Unexport elv_register_queue() and elv_unregister_queue() Bart Van Assche
2018-01-18 16:27 ` Christoph Hellwig
2018-01-17 19:48 ` [PATCH v2 2/3] block: Document scheduler modification locking requirements Bart Van Assche
2018-01-18 16:27 ` Christoph Hellwig [this message]
2018-01-17 19:48 ` [PATCH v2 3/3] block: Protect less code with sysfs_lock in blk_{un,}register_queue() Bart Van Assche
2018-01-18 16:28 ` Christoph Hellwig
2018-01-18 19:55 ` [PATCH v2 0/3] Avoid that blk_{un,}register_queue() trigger lock inversion Jens Axboe
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=20180118162745.GC26078@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=bart.vanassche@wdc.com \
--cc=linux-block@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 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.