linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Souptick Joarder <jrdr.linux@gmail.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH] fs: proc: Adding new typedef vm_fault_t
Date: Thu, 31 May 2018 10:01:04 +0530	[thread overview]
Message-ID: <CAFqt6zaepaSFQjLh7me1ps9b27xnYovvKErUE=y=TRn=Zo2Lgg@mail.gmail.com> (raw)
In-Reply-To: <CAFqt6zYo9YLaVzL1iSqz6xw=_VLHjq7Wc6ZJzdM1qPmMth132g@mail.gmail.com>

On Mon, May 14, 2018 at 11:46 PM, Souptick Joarder <jrdr.linux@gmail.com> wrote:
> On Sun, Apr 15, 2018 at 1:29 AM, Souptick Joarder <jrdr.linux@gmail.com> wrote:
>> Use new return type vm_fault_t for fault handler.
>>
>> Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
>> Reviewed-by: Matthew Wilcox <mawilcox@microsoft.com>
>> ---
>>  fs/proc/vmcore.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/fs/proc/vmcore.c b/fs/proc/vmcore.c
>> index a45f0af..7243e94 100644
>> --- a/fs/proc/vmcore.c
>> +++ b/fs/proc/vmcore.c
>> @@ -265,7 +265,7 @@ static ssize_t read_vmcore(struct file *file, char __user *buffer,
>>   * On s390 the fault handler is used for memory regions that can't be mapped
>>   * directly with remap_pfn_range().
>>   */
>> -static int mmap_vmcore_fault(struct vm_fault *vmf)
>> +static vm_fault_t mmap_vmcore_fault(struct vm_fault *vmf)
>>  {
>>  #ifdef CONFIG_S390
>>         struct address_space *mapping = vmf->vma->vm_file->f_mapping;
>> --
>> 1.9.1
>>
>
> Any comment on this patch ? We would like to get this patch in
> queue for 4.18.

If no comment, we would like to get this patch in queue
for 4.18.

      reply	other threads:[~2018-05-31  4:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-14 19:59 [PATCH] fs: proc: Adding new typedef vm_fault_t Souptick Joarder
2018-05-14 18:16 ` Souptick Joarder
2018-05-31  4:31   ` Souptick Joarder [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='CAFqt6zaepaSFQjLh7me1ps9b27xnYovvKErUE=y=TRn=Zo2Lgg@mail.gmail.com' \
    --to=jrdr.linux@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.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).