From: Jens Axboe <axboe@kernel.dk>
To: Bart Van Assche <bvanassche@acm.org>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 0/8] Improve block layer function documentation
Date: Fri, 31 May 2019 10:58:09 -0600 [thread overview]
Message-ID: <f97c1c4b-b5f6-8bfc-bd11-2907a8953e46@kernel.dk> (raw)
In-Reply-To: <20190531000053.64053-1-bvanassche@acm.org>
On 5/30/19 6:00 PM, Bart Van Assche wrote:
> Hi Jens,
>
> This is a series with eight patches that address source code comments. Most
> patches suppress kernel-doc warnings that appear when building with W=1. Please
> consider these patches.
Thanks Bart, applied.
--
Jens Axboe
prev parent reply other threads:[~2019-05-31 16:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 0:00 [PATCH 0/8] Improve block layer function documentation Bart Van Assche
2019-05-31 0:00 ` [PATCH 1/8] block/partitions/ldm: Convert a kernel-doc header into a non-kernel-doc header Bart Van Assche
2019-05-31 2:00 ` Chaitanya Kulkarni
2019-05-31 0:00 ` [PATCH 2/8] block: Convert blk_invalidate_devt() " Bart Van Assche
2019-05-31 2:00 ` Chaitanya Kulkarni
2019-05-31 0:00 ` [PATCH 3/8] block: Fix throtl_pending_timer_fn() kernel-doc header Bart Van Assche
2019-05-31 2:01 ` Chaitanya Kulkarni
2019-05-31 2:08 ` Kees Cook
2019-05-31 0:00 ` [PATCH 4/8] block: Fix blk_mq_*_map_queues() kernel-doc headers Bart Van Assche
2019-05-31 2:01 ` Chaitanya Kulkarni
2019-05-31 0:00 ` [PATCH 5/8] block: Fix rq_qos_wait() kernel-doc header Bart Van Assche
2019-05-31 2:02 ` Chaitanya Kulkarni
2019-05-31 0:00 ` [PATCH 6/8] block: Fix bsg_setup_queue() " Bart Van Assche
2019-05-31 2:02 ` Chaitanya Kulkarni
2019-05-31 0:00 ` [PATCH 7/8] blk-mq: Fix spelling in a source code comment Bart Van Assche
2019-05-31 2:03 ` Chaitanya Kulkarni
2019-05-31 0:00 ` [PATCH 8/8] blk-mq: Document the blk_mq_hw_queue_to_node() arguments Bart Van Assche
2019-05-31 2:04 ` Chaitanya Kulkarni
2019-05-31 16:58 ` 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=f97c1c4b-b5f6-8bfc-bd11-2907a8953e46@kernel.dk \
--to=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox