From: "André Almeida" <andrealmeid@collabora.com>
To: Bart Van Assche <bvanassche@acm.org>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: axboe@kernel.dk, kernel@collabora.com, krisman@collabora.com
Subject: Re: [PATCH 1/1] blk-mq: fill header with kernel-doc
Date: Mon, 30 Sep 2019 21:01:42 -0300 [thread overview]
Message-ID: <349b7e6a-fcf3-e1f3-2674-50f316bda9bf@collabora.com> (raw)
In-Reply-To: <845be3ae-f7f4-4e80-ee26-30a03a8af8b4@acm.org>
On 9/30/19 7:01 PM, Bart Van Assche wrote:
> On 9/30/19 12:48 PM, André Almeida wrote:
>> Insert documentation for structs, enums and functions at header file.
>> Format existing and new comments at struct blk_mq_ops as
>> kernel-doc comments.
>
> Hi André,
>
> Seeing the documentation being improved is great. However, this patch
> conflicts with a patch series in my tree and that I plan to post soon.
> So I would appreciate it if this patch would be withheld until after my
> patch series has been accepted.
>
Sure, no problem. If it helps the workflow, I could rebase my patch at
the top of your tree.
> Thanks,
>
> Bart.
>
next prev parent reply other threads:[~2019-10-01 0:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 19:48 [PATCH 1/1] blk-mq: fill header with kernel-doc André Almeida
[not found] ` <CGME20190930211400epcas2p4253bdc8cc3630f87d7e955cd23fdf1f2@epcms2p6>
2019-09-30 21:54 ` Minwoo Im
2019-10-01 0:01 ` André Almeida
2019-09-30 22:01 ` Bart Van Assche
2019-10-01 0:01 ` André Almeida [this message]
2019-10-02 3:33 ` Jens Axboe
2019-10-02 17:18 ` André Almeida
2019-10-02 20:27 ` Bart Van Assche
2019-10-02 21:05 ` André Almeida
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=349b7e6a-fcf3-e1f3-2674-50f316bda9bf@collabora.com \
--to=andrealmeid@collabora.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=kernel@collabora.com \
--cc=krisman@collabora.com \
--cc=linux-block@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 NNTP newsgroup(s).