From: Jason Gunthorpe <jgg@nvidia.com>
To: YueHaibing <yuehaibing@huawei.com>
Cc: dledford@redhat.com, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] IB/ipoib: use DEVICE_ATTR_*() macro
Date: Fri, 28 May 2021 20:41:58 -0300 [thread overview]
Message-ID: <20210528234158.GA3874396@nvidia.com> (raw)
In-Reply-To: <20210526132753.3092-1-yuehaibing@huawei.com>
On Wed, May 26, 2021 at 09:27:53PM +0800, YueHaibing wrote:
> Use DEVICE_ATTR_*() helper instead of plain DEVICE_ATTR,
> which makes the code a bit shorter and easier to read.
>
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> ---
> drivers/infiniband/ulp/ipoib/ipoib_cm.c | 10 ++++----
> drivers/infiniband/ulp/ipoib/ipoib_main.c | 28 +++++++++++------------
> drivers/infiniband/ulp/ipoib/ipoib_vlan.c | 6 ++---
> 3 files changed, 21 insertions(+), 23 deletions(-)
Applied to for-next. I touched it with clang-format to fix the spacing
issues.
Thanks,
Jason
prev parent reply other threads:[~2021-05-28 23:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 13:27 [PATCH -next] IB/ipoib: use DEVICE_ATTR_*() macro YueHaibing
2021-05-28 23:41 ` 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=20210528234158.GA3874396@nvidia.com \
--to=jgg@nvidia.com \
--cc=dledford@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=yuehaibing@huawei.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