From: miaoqinglang <miaoqinglang@huawei.com>
To: Pavel Machek <pavel@denx.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
<linux-bcache@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] memory: Convert to DEFINE_SHOW_ATTRIBUTE
Date: Mon, 20 Jul 2020 10:02:19 +0800 [thread overview]
Message-ID: <55762551-4f14-b7f8-c2ae-e93e75ef3299@huawei.com> (raw)
In-Reply-To: <20200717211420.GA4140@amd>
在 2020/7/18 5:14, Pavel Machek 写道:
> On Thu 2020-07-16 17:03:03, Qinglang Miao wrote:
>> From: Yongqiang Liu <liuyongqiang13@huawei.com>
>>
>> Use DEFINE_SHOW_ATTRIBUTE macro to simplify the code.
>>
>> Signed-off-by: Yongqiang Liu <liuyongqiang13@huawei.com>
>> ---
>> drivers/memory/emif.c | 22 ++--------------------
>> drivers/memory/tegra/tegra124-emc.c | 14 +-------------
>> 2 files changed, 3 insertions(+), 33 deletions(-)
>>
>> diff --git a/drivers/memory/emif.c b/drivers/memory/emif.c
>> index 58a82eea5..aab8ddad7 100644
>> --- a/drivers/memory/emif.c
>> +++ b/drivers/memory/emif.c
>> @@ -131,16 +131,7 @@ static int emif_regdump_show(struct seq_file *s, void *unused)
>> return 0;
>> }
>>
>> -static int emif_regdump_open(struct inode *inode, struct file *file)
>> -{
>> - return single_open(file, emif_regdump_show, inode->i_private);
>> -}
>> -
>> -static const struct file_operations emif_regdump_fops = {
>> - .open = emif_regdump_open,
>> - .read_iter = seq_read_iter,
>> - .release = single_release,
>> -};
>> +DEFINE_SHOW_ATTRIBUTE(emif_regdump);
>
> This is not equivalent (and I guess changelog should mention that).
>
> Along with other changes, we get:
>
> .owner = THIS_MODULE,
> .llseek = seq_lseek,
>
> . Is that okay thing to add?
> Pavel
>
Hi Pavel,
You're right, I should of mention it in changelog.
There's no impact theoretically with these two changes. Here's my thoughs:
1. The llseek method is used to change the current read/write position
in a file which can be ignored if you don't use it.
2. The owner is not even a method. Instead, it is a pointer to the
module that “owns” this structure; it is used by the kernel to maintain
the module's usage count which I believe can be ignored.
If you don't mind I can send a new patch with more specific changelog.
Thanks.
Qinglang
.
next prev parent reply other threads:[~2020-07-20 2:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 9:03 Qinglang Miao
2020-07-17 21:14 ` Pavel Machek
2020-07-20 2:02 ` miaoqinglang [this message]
2020-09-17 12:48 ` miaoqinglang
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=55762551-4f14-b7f8-c2ae-e93e75ef3299@huawei.com \
--to=miaoqinglang@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@denx.de \
--cc=ssantosh@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
all inboxes | Powered by JetHome®