From: asmadeus@codewreck.org
To: YueHaibing <yuehaibing@huawei.com>
Cc: ericvh@gmail.com, lucho@ionkov.net, davem@davemloft.net,
kuba@kernel.org, v9fs-developer@lists.sourceforge.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net/9p: use DEVICE_ATTR_RO macro
Date: Wed, 19 May 2021 12:26:42 +0900 [thread overview]
Message-ID: <YKSFchOrlTUxBto1@codewreck.org> (raw)
In-Reply-To: <20210519025639.12108-1-yuehaibing@huawei.com>
YueHaibing wrote on Wed, May 19, 2021 at 10:56:39AM +0800:
> Use DEVICE_ATTR_RO helper instead of plain DEVICE_ATTR,
> which makes the code a bit shorter and easier to read.
>
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
Sure, why not.
Will queue to -next tomorrow-ish
--
Dominique
prev parent reply other threads:[~2021-05-19 3:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 2:56 [PATCH net-next] net/9p: use DEVICE_ATTR_RO macro YueHaibing
2021-05-19 3:26 ` asmadeus [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=YKSFchOrlTUxBto1@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=davem@davemloft.net \
--cc=ericvh@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=netdev@vger.kernel.org \
--cc=v9fs-developer@lists.sourceforge.net \
--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;
as well as URLs for NNTP newsgroup(s).