From: Souptick Joarder <jrdr.linux@gmail.com>
To: Eric Van Hensbergen <ericvh@gmail.com>,
rminnich@sandia.gov, Latchesar Ionkov <lucho@ionkov.net>
Cc: v9fs-developer@lists.sourceforge.net,
Matthew Wilcox <willy@infradead.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs: 9p: Adding new return type vm_fault_t
Date: Tue, 19 Jun 2018 10:37:04 +0530 [thread overview]
Message-ID: <CAFqt6zaueQ6FW-NTgOUboPjpMReHBiGOAFG2dadOKnZYz_QB7Q@mail.gmail.com> (raw)
In-Reply-To: <CAFqt6zaDdhG9=ak1ufeY2x8sr+nin8e+cgMQoi=-2o41uS5jxA@mail.gmail.com>
On Sun, Jun 10, 2018 at 3:26 PM, Souptick Joarder <jrdr.linux@gmail.com> wrote:
> On Sun, Jun 10, 2018 at 3:26 PM, Souptick Joarder <jrdr.linux@gmail.com> wrote:
>> Use new return type vm_fault_t for page_mkwrite
>> handler.
>>
>> Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
>> Reviewed-by: Matthew Wilcox <mawilcox@microsoft.com>
>> ---
>> fs/9p/vfs_file.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/fs/9p/vfs_file.c b/fs/9p/vfs_file.c
>> index 03c9e32..5f2e48d 100644
>> --- a/fs/9p/vfs_file.c
>> +++ b/fs/9p/vfs_file.c
>> @@ -533,7 +533,7 @@ int v9fs_file_fsync_dotl(struct file *filp, loff_t start, loff_t end,
>> return retval;
>> }
>>
>> -static int
>> +static vm_fault_t
>> v9fs_vm_page_mkwrite(struct vm_fault *vmf)
>> {
>> struct v9fs_inode *v9inode;
>> --
>> 1.9.1
>>
>
> Eric, as requested, posted it in net-dev and lkml mailing list.
Eric, any comment on this patch ?
prev parent reply other threads:[~2018-06-19 5:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-10 9:56 [PATCH] fs: 9p: Adding new return type vm_fault_t Souptick Joarder
2018-06-10 9:56 ` Souptick Joarder
2018-06-19 5:07 ` 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=CAFqt6zaueQ6FW-NTgOUboPjpMReHBiGOAFG2dadOKnZYz_QB7Q@mail.gmail.com \
--to=jrdr.linux@gmail.com \
--cc=ericvh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=netdev@vger.kernel.org \
--cc=rminnich@sandia.gov \
--cc=v9fs-developer@lists.sourceforge.net \
--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).