From: Steffen Maier <maier@linux.ibm.com>
To: linux-btrace@vger.kernel.org
Subject: Re: [PATCH 1/2] blkparse: remove duplicated entry for flag M
Date: Mon, 09 Apr 2018 14:33:10 +0000 [thread overview]
Message-ID: <2e2165c8-24ca-e7ec-fbbd-4beca9eef743@linux.ibm.com> (raw)
In-Reply-To: <3b4a1adbd6869ab90dd2818e0248b4a8c425c188.1523092071.git.zhangweiping@didichuxing.com>
On 04/07/2018 11:12 AM, Weiping Zhang wrote:
> remove dupliated entry 'M' for man page of blkparse.
>
> Signed-off-by: Weiping Zhang <zhangweiping@didichuxing.com>
> ---
> doc/blkparse.1 | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/doc/blkparse.1 b/doc/blkparse.1
> index be9b34b..b1cb6ef 100644
> --- a/doc/blkparse.1
> +++ b/doc/blkparse.1
> @@ -243,10 +243,6 @@ Same as the back merge, except this i/o ends where a previously inserted
> requests starts.
>
> .HP 4
> -\fBM --front or back merge\fR
> -One of the above
> -
> -.HP 4
> \fBM -- front or back merge\fR
> One of the above.
>
I also found this (and other things) and plan to submit them later.
Additionally, I had the impression that 'M' is nowadays always a "back
merge", not "front or back merge".
Anyway, dropping the duplicate seems right:
Reviewed-by: Steffen Maier <maier@linux.ibm.com>
--
Mit freundlichen Grüßen / Kind regards
Steffen Maier
Linux on z Systems Development
IBM Deutschland Research & Development GmbH
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschaeftsfuehrung: Dirk Wittkopp
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
next prev parent reply other threads:[~2018-04-09 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-07 9:12 [PATCH 1/2] blkparse: remove duplicated entry for flag M Weiping Zhang
2018-04-09 14:33 ` Steffen Maier [this message]
2018-04-09 14:36 ` 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=2e2165c8-24ca-e7ec-fbbd-4beca9eef743@linux.ibm.com \
--to=maier@linux.ibm.com \
--cc=linux-btrace@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