From: Jason Gunthorpe <jgg@ziepe.ca>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>, Tejun Heo <tj@kernel.org>,
Li Zefan <lizefan@huawei.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Parav Pandit <parav@mellanox.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
cgroups <cgroups@vger.kernel.org>,
Leon Romanovsky <leonro@mellanox.com>
Subject: Re: [PATCH rdma-next] IB/core: Simplify rdma cgroup registration
Date: Fri, 18 Jan 2019 13:44:16 -0700 [thread overview]
Message-ID: <20190118204416.GA7101@ziepe.ca> (raw)
In-Reply-To: <20190117181415.28566-1-leon@kernel.org>
On Thu, Jan 17, 2019 at 08:14:15PM +0200, Leon Romanovsky wrote:
> From: Parav Pandit <parav@mellanox.com>
>
> RDMA cgroup registration routine always returns success,
> so simplify function to be void and run clang formatter
> over whole CONFIG_CGROUP_RDMA art of core_priv.h.
>
> This reduces unwinding error path for regular registration and
> future net namespace change functionality for rdma device.
>
> Signed-off-by: Parav Pandit <parav@mellanox.com>
> Signed-off-by: Leon Romanovsky <leonro@mellanox.com>
> Acked-by: Tejun Heo <tj@kernel.org>
> ---
> drivers/infiniband/core/cgroup.c | 5 ++---
> drivers/infiniband/core/core_priv.h | 17 +++++++++++------
> drivers/infiniband/core/device.c | 8 +-------
> include/linux/cgroup_rdma.h | 2 +-
> kernel/cgroup/rdma.c | 5 +----
> 5 files changed, 16 insertions(+), 21 deletions(-)
Applied to for-next
Thanks,
Jason
prev parent reply other threads:[~2019-01-18 20:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 18:14 [PATCH rdma-next] IB/core: Simplify rdma cgroup registration Leon Romanovsky
2019-01-18 16:16 ` Tejun Heo
2019-01-18 20:44 ` Jason Gunthorpe [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=20190118204416.GA7101@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=cgroups@vger.kernel.org \
--cc=dledford@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=leon@kernel.org \
--cc=leonro@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=parav@mellanox.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).