All of lore.kernel.org
 help / color / mirror / Atom feed
From: Glyn Normington <gnormington@gopivotal.com>
To: Tejun Heo <tj@kernel.org>
Cc: Li Zefan <lizefan@huawei.com>,
	linux-kernel@vger.kernel.org,
	Steve Powell <spowell@gopivotal.com>
Subject: Re: [PATCH] control groups: documentation improvements
Date: Fri, 14 Mar 2014 14:04:46 +0000	[thread overview]
Message-ID: <53230C7E.7060607@gopivotal.com> (raw)
In-Reply-To: <20140314140136.GF12613@htj.dyndns.org>

On 14/03/2014 14:01, Tejun Heo wrote:
> Hey,
>
> On Fri, Mar 14, 2014 at 01:30:29PM +0000, Glyn Normington wrote:
>> Hi Li
>>
>> Thanks! Inline...
>>
>> Tejun: Li agrees with our reasoning on the "views" issue, but we'd
>> like your feedback too in preparation for a new patch.
> I don't really mind as long as it's not wrong.  Can't be worse than
> now anyway.
:-)
>
> Thanks.
>

  reply	other threads:[~2014-03-14 14:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-10 11:39 [PATCH] control groups: documentation improvements Glyn Normington
2014-03-10 14:07 ` Tejun Heo
2014-03-10 14:17   ` Glyn Normington
2014-03-10 14:20     ` Tejun Heo
2014-03-13 16:04       ` Glyn Normington
2014-03-14  1:33         ` Li Zefan
2014-03-14 13:30           ` Glyn Normington
2014-03-14 14:01             ` Tejun Heo
2014-03-14 14:04               ` Glyn Normington [this message]
2014-04-02 12:43                 ` [PATCH v2] " Glyn Normington
2014-04-02 13:17                   ` [PATCH v3] " Glyn Normington
2014-04-16 21:00                     ` Tejun Heo
2014-04-17 10:46                       ` [PATCH v4] " Glyn Normington
2014-04-17 13:16                         ` Tejun Heo
2014-04-17 13:45                           ` Glyn Normington
2014-04-17 13:55                             ` Tejun Heo
2014-04-17 14:51                               ` Glyn Normington
2014-04-17 14:57                                 ` Tejun Heo

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=53230C7E.7060607@gopivotal.com \
    --to=gnormington@gopivotal.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=spowell@gopivotal.com \
    --cc=tj@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 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.