From: Christoph Hellwig <hch@lst.de>
To: Tejun Heo <tj@kernel.org>
Cc: Parav Pandit <pandit.parav@gmail.com>,
cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
lizefan@huawei.com, hannes@cmpxchg.org, dledford@redhat.com,
liranl@mellanox.com, sean.hefty@intel.com,
jgunthorpe@obsidianresearch.com, haggaie@mellanox.com,
corbet@lwn.net, james.l.morris@oracle.com, serge@hallyn.com,
ogerlitz@mellanox.com, matanb@mellanox.com,
akpm@linux-foundation.org, linux-security-module@vger.kernel.org,
hch@lst.de
Subject: Re: [PATCHv11 0/3] rdmacg: IB/core: rdma controller support
Date: Thu, 25 Aug 2016 09:32:26 +0200 [thread overview]
Message-ID: <20160825073226.GA18183@lst.de> (raw)
In-Reply-To: <20160824211747.GV8185@htj.duckdns.org>
On Wed, Aug 24, 2016 at 05:17:47PM -0400, Tejun Heo wrote:
> Looks good to me. I just have a nit in the documentation. Christoph,
> what do you think?
Looks reasonable from a quick look, but I didn't do a full review yet.
next prev parent reply other threads:[~2016-08-25 7:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 12:33 [PATCHv11 0/3] rdmacg: IB/core: rdma controller support Parav Pandit
2016-08-22 12:33 ` [PATCHv11 2/3] IB/core: added support to use rdma cgroup controller Parav Pandit
2016-08-22 12:33 ` [PATCHv11 3/3] rdmacg: Added documentation for rdmacg Parav Pandit
[not found] ` <1471869231-15576-4-git-send-email-pandit.parav-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-08-24 21:18 ` Tejun Heo
2016-08-24 22:55 ` Rami Rosen
2016-08-25 7:58 ` Parav Pandit
[not found] ` <1471869231-15576-1-git-send-email-pandit.parav-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-08-22 12:33 ` [PATCHv11 1/3] rdmacg: Added rdma cgroup controller Parav Pandit
2016-08-24 21:17 ` [PATCHv11 0/3] rdmacg: IB/core: rdma controller support Tejun Heo
2016-08-25 7:32 ` Christoph Hellwig [this message]
[not found] ` <20160825073226.GA18183-jcswGhMUV9g@public.gmane.org>
2016-08-25 8:00 ` Parav Pandit
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=20160825073226.GA18183@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=dledford@redhat.com \
--cc=haggaie@mellanox.com \
--cc=hannes@cmpxchg.org \
--cc=james.l.morris@oracle.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=liranl@mellanox.com \
--cc=lizefan@huawei.com \
--cc=matanb@mellanox.com \
--cc=ogerlitz@mellanox.com \
--cc=pandit.parav@gmail.com \
--cc=sean.hefty@intel.com \
--cc=serge@hallyn.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).