All of lore.kernel.org
 help / color / mirror / Atom feed
From: "gnehzuil.lzheng@gmail.com" <gnehzuil.lzheng@gmail.com>
To: Rob Landley <rob@landley.net>
Cc: Sami Kerola <kerolasa@gmail.com>, Sami Kerola <kerolasa@iki.fi>,
	Jens Axboe <axboe@kernel.dk>,
	Bernhard Voelker <mail@bernhard-voelker.de>,
	Zheng Liu <wenqing.lz@taobao.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	util-linux@vger.kernel.org
Subject: Re: [PATCH] docs: block: update ioprio.txt
Date: Thu, 21 Jun 2012 18:19:08 +0800	[thread overview]
Message-ID: <4FE2F51C.1060106@gmail.com> (raw)
In-Reply-To: <4FE2A825.1060103@landley.net>

On 06/21/2012 12:50 PM, Rob Landley wrote:

> On 06/19/2012 05:27 AM, Zheng Liu wrote:
>> Hi Sami,
>>
>> [You forgot to CC'd other developers and mailing list]
>>
>> On Tue, Jun 19, 2012 at 10:54:41AM +0200, Sami Kerola wrote:
>>> Hi Zheng,
>>>
>>> Wouldn't a patch such as below be better?
>>
>> Looks good to me.  But, IMHO, if reader cannot access Internet, my patch
>> maybe is better for them.  The original writer is not me.  So I don't
>> understand the original idea that puts ionice source code in here.  I
>> think that Jens can do the final decision.
>>
>> Hi Jens,
>>
>> What's your opintion about Sami's and my patch?
> 
> I note that it's nice to have a reference implementation for nontrivial
> things. Also, util-linux isn't the end-all and be-all of linux
> userspace: busybox has an ionice, and I plan to add an ionice
> implementation to toybox as well.
> 
> So fixing reference code is good. That said, this isn't a "fix", this is
> a rewrite adding all sorts of unnecessary complexity
> (internationalization? strtos32_or_error() instead of strtol()?) that
> makes it much _less_ effective as reference code.


OK.  I will repost a second version later.

Regards,
Zheng

      parent reply	other threads:[~2012-06-21 10:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-19  8:51 [PATCH] docs: block: update ioprio.txt Zheng Liu
2012-06-19 10:19 ` Karel Zak
     [not found] ` <CAG27Bk2tXprRfMfYOVdWtwSbjw5Rw9Kxs6Wns+Gm65m3hoJawg@mail.gmail.com>
2012-06-19 10:27   ` Zheng Liu
2012-06-21  4:50     ` Rob Landley
2012-06-21  6:50       ` Sami Kerola
2012-06-21 10:19       ` gnehzuil.lzheng [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=4FE2F51C.1060106@gmail.com \
    --to=gnehzuil.lzheng@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=kerolasa@gmail.com \
    --cc=kerolasa@iki.fi \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mail@bernhard-voelker.de \
    --cc=rob@landley.net \
    --cc=util-linux@vger.kernel.org \
    --cc=wenqing.lz@taobao.com \
    /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.