From: Tejun Heo <tj@kernel.org>
To: Parav Pandit <pandit.parav@gmail.com>
Cc: 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,
hch@lst.de, 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
Subject: Re: [PATCHv13 0/3] rdmacg: IB/core: rdma controller support
Date: Mon, 9 Jan 2017 08:02:21 -0500 [thread overview]
Message-ID: <20170109130221.GD10904@mtj.duckdns.org> (raw)
In-Reply-To: <1480705637-2986-1-git-send-email-pandit.parav@gmail.com>
On Fri, Dec 02, 2016 at 07:07:14PM +0000, Parav Pandit wrote:
> Patch is generated and tested against below Doug's linux-rdma
> git tree.
> URL: git://git.kernel.org/pub/scm/linux/kernel/git/dledford/rdma.git
> Branch: master
>
> Patchset is also compiled and tested against below Tejun's cgroup tree
> using cgroup v2 mode.
> URL: git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git
> Branch: master
Except for the minor nits, all look good to me. Can you please
refresh on top of cgroup/for-4.11 and the rdma devel branch? Please
note that cgroup/for-4.11 moved the cgroup source files under
kernel/cgroup/.
Thanks!
--
tejun
next prev parent reply other threads:[~2017-01-09 13:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 19:07 [PATCHv13 0/3] rdmacg: IB/core: rdma controller support Parav Pandit
2016-12-02 19:07 ` [PATCHv13 1/3] rdmacg: Added rdma cgroup controller Parav Pandit
2017-01-09 12:58 ` Tejun Heo
2016-12-02 19:07 ` [PATCHv13 2/3] IB/core: added support to use " Parav Pandit
2017-01-09 13:00 ` Tejun Heo
2016-12-02 19:07 ` [PATCHv13 3/3] rdmacg: Added documentation for rdmacg Parav Pandit
2016-12-05 19:35 ` [PATCHv13 0/3] rdmacg: IB/core: rdma controller support Tejun Heo
2016-12-06 2:05 ` Parav Pandit
2017-01-09 13:02 ` Tejun Heo [this message]
2017-01-09 20:01 ` Parav Pandit
2017-01-09 20:06 ` 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=20170109130221.GD10904@mtj.duckdns.org \
--to=tj@kernel.org \
--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=hch@lst.de \
--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 \
/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).