All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhang Zhen <zhenzhang.zhang@huawei.com>
To: <dedekind1@gmail.com>
Cc: wangnan0@huawei.com,
	MTD Maling List <linux-mtd@lists.infradead.org>,
	Adrian Hunter <adrian.hunter@intel.com>
Subject: Re: [PATCH v2] ubifs: refactor ubifs_file_mmap()
Date: Tue, 29 Jul 2014 11:50:39 +0800	[thread overview]
Message-ID: <53D71A0F.9070008@huawei.com> (raw)
In-Reply-To: <1406564713.23376.39.camel@sauron.fi.intel.com>

On 2014/7/29 0:25, Artem Bityutskiy wrote:
> On Tue, 2014-07-22 at 14:28 +0800, Zhang Zhen wrote:
>> generic_file_mmap() set vma->vm_ops = &generic_file_vm_ops,
>> then ubifs_file_mmap set vma->vm_ops = &ubifs_file_vm_ops.
>> So it is redundant.
>> And there is no kind of file does not supply page reading function
>> in ubifs. The readpage() check up for mmap file in generic_file_mmap()
>> is not needed.
>>
>> So remove the call of generic_file_mmap().
>>
>> Change v1 -> v2:
>> - deleted the mapping variable
>> Signed-off-by: Zhang Zhen <zhenzhang.zhang@huawei.com>
> 
> Hi, I am not sure about this patch. 'generic_file_mmap()' covers !
> CONFIG_MMU case too, for example.
> 
Yes, I missed that. We can add #ifdef CONFIG_MMU in ubifs_file_mmap().
Considering the patch itself is not important changes, we can give up
this patch, remain the same.

What do you think?

Thanks for your comments!
> Thanks!
> 

  reply	other threads:[~2014-07-29  3:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1406010548-13996-1-git-send-email-zhenzhang.zhang@huawei.com>
2014-07-22  6:28 ` [PATCH v2] ubifs: refactor ubifs_file_mmap() Zhang Zhen
2014-07-28 16:25   ` Artem Bityutskiy
2014-07-29  3:50     ` Zhang Zhen [this message]
2014-07-29  7:20       ` Artem Bityutskiy
2014-07-29  7:33         ` Zhang Zhen

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=53D71A0F.9070008@huawei.com \
    --to=zhenzhang.zhang@huawei.com \
    --cc=adrian.hunter@intel.com \
    --cc=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=wangnan0@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.