All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: <tglx@linutronix.de>, <linux-kernel@vger.kernel.org>,
	<linux-doc@vger.kernel.org>
Subject: Re: [PATCH] hrtimers: doc cleanup
Date: Thu, 21 Apr 2016 18:25:41 +0800	[thread overview]
Message-ID: <5718AAA5.1080305@cn.fujitsu.com> (raw)
In-Reply-To: <20160421035606.619dee77@lwn.net>

Hi jon
     Thanks for your quick respond for my 1st patch here.

On 04/21/2016 05:56 PM, Jonathan Corbet wrote:
> On Thu, 21 Apr 2016 17:09:54 +0800
> Cao jin <caoj.fnst@cn.fujitsu.com> wrote:
>
>> -  wheel concept, it cannot be 'designed out' without unevitably
>> -  degrading other portions of the timers.c code in an unacceptable way.
>> +  wheel concept, it cannot be 'designed out' without inevitably
>> +  degrading other portions of the timers.c code in an acceptable way.
>
> This change is incorrect - "unacceptable" is exactly what the writer
> wanted to say here.
>
*it cannot be 'designed out' without inevitably degrading other portions 
of the timers.c code in an unacceptable way*

equals

*it can be 'designed out' ... in an acceptable way*, I think.

So, just from semantics, my feeling is, *it cannot be 'designed out' in 
an acceptable way* is the reason why integration is hard. Am I still wrong?

-- 
Yours Sincerely,

Cao jin

  reply	other threads:[~2016-04-21 10:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-21  9:09 [PATCH] hrtimers: doc cleanup Cao jin
2016-04-21  9:56 ` Jonathan Corbet
2016-04-21 10:25   ` Cao jin [this message]
2016-04-21 13:23     ` Jonathan Corbet
2016-04-21 13:36       ` Cao jin

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=5718AAA5.1080305@cn.fujitsu.com \
    --to=caoj.fnst@cn.fujitsu.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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.