Linux btrace development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: linux-btrace@vger.kernel.org
Subject: Re: [PATCH 1/2] blkparse: remove duplicated entry for flag M
Date: Mon, 09 Apr 2018 14:36:16 +0000	[thread overview]
Message-ID: <8ee57a6d-5519-5ca1-bfaa-abe77db865b3@kernel.dk> (raw)
In-Reply-To: <3b4a1adbd6869ab90dd2818e0248b4a8c425c188.1523092071.git.zhangweiping@didichuxing.com>

On 4/9/18 8:33 AM, Steffen Maier wrote:
> 
> 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".

'M' is a back merge, 'F' is a front merge.

-- 
Jens Axboe


      parent reply	other threads:[~2018-04-09 14:36 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
2018-04-09 14:36 ` 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=8ee57a6d-5519-5ca1-bfaa-abe77db865b3@kernel.dk \
    --to=axboe@kernel.dk \
    --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