From: YueHaibing <yuehaibing@huawei.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>, <jgross@suse.com>,
<sstabellini@kernel.org>
Cc: <xen-devel@lists.xenproject.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] xen/pcpu: Use DEVICE_ATTR_RW macro
Date: Tue, 25 May 2021 14:17:33 +0800 [thread overview]
Message-ID: <e2f4309d-e53a-1511-a732-9cf5c5217d55@huawei.com> (raw)
In-Reply-To: <c27b37e3-7d4b-1ed1-2b8c-1fbde6e30c3b@oracle.com>
On 2021/5/24 20:48, Boris Ostrovsky wrote:
>
> On 5/23/21 3:02 AM, YueHaibing wrote:
>> Use DEVICE_ATTR_RW helper instead of plain DEVICE_ATTR,
>> which makes the code a bit shorter and easier to read.
>>
>> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
>
>
> Do you think you can also make similar change in drivers/xen/xen-balloon.c and drivers/xen/xenbus/xenbus_probe.c?
>
Sure, will do that in v2.
>
>
> Thanks.
>
> -boris
>
> .
>
prev parent reply other threads:[~2021-05-25 6:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-23 7:02 [PATCH -next] xen/pcpu: Use DEVICE_ATTR_RW macro YueHaibing
2021-05-24 12:48 ` Boris Ostrovsky
2021-05-25 6:17 ` YueHaibing [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=e2f4309d-e53a-1511-a732-9cf5c5217d55@huawei.com \
--to=yuehaibing@huawei.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).