All of lore.kernel.org
 help / color / mirror / Atom feed
From: Souptick Joarder <jrdr.linux@gmail.com>
To: willy@infradead.org, corbet@lwn.net, darrick.wong@oracle.com,
	gregkh@linuxfoundation.org, mszeredi@redhat.com,
	viro@zeniv.linux.org.uk, seanga2@gmail.com, jrdr.linux@gmail.com
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	ajitn.linux@gmail.com, brajeswar.linux@gmail.com,
	sabyasachi.linux@gmail.com
Subject: [PATCH] mm: Introduce new type vm_fault_t
Date: Sun, 22 Jul 2018 18:31:34 +0530	[thread overview]
Message-ID: <20180722130134.GA31321@jordon-HP-15-Notebook-PC> (raw)

We have introduce a new return type vm_fault_t for
fault, page_mkwrite and pfn_mkwrite handlers. Update
the document for the same

Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
---
 Documentation/filesystems/Locking | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/filesystems/Locking b/Documentation/filesystems/Locking
index 2c39133..233413b 100644
--- a/Documentation/filesystems/Locking
+++ b/Documentation/filesystems/Locking
@@ -537,9 +537,9 @@ More details about quota locking can be found in fs/dquot.c.
 prototypes:
 	void (*open)(struct vm_area_struct*);
 	void (*close)(struct vm_area_struct*);
-	int (*fault)(struct vm_area_struct*, struct vm_fault *);
-	int (*page_mkwrite)(struct vm_area_struct *, struct vm_fault *);
-	int (*pfn_mkwrite)(struct vm_area_struct *, struct vm_fault *);
+	vm_fault_t (*fault)(struct vm_area_struct*, struct vm_fault *);
+	vm_fault_t (*page_mkwrite)(struct vm_area_struct *, struct vm_fault *);
+	vm_fault_t (*pfn_mkwrite)(struct vm_area_struct *, struct vm_fault *);
 	int (*access)(struct vm_area_struct *, unsigned long, void*, int, int);
 
 locking rules:
-- 
1.9.1

--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Souptick Joarder <jrdr.linux@gmail.com>
To: willy@infradead.org, corbet@lwn.net, darrick.wong@oracle.com,
	gregkh@linuxfoundation.org, mszeredi@redhat.com,
	viro@zeniv.linux.org.uk, seanga2@gmail.com, jrdr.linux@gmail.com
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	ajitn.linux@gmail.com, brajeswar.linux@gmail.com,
	sabyasachi.linux@gmail.com
Subject: [PATCH] mm: Introduce new type vm_fault_t
Date: Sun, 22 Jul 2018 18:31:34 +0530	[thread overview]
Message-ID: <20180722130134.GA31321@jordon-HP-15-Notebook-PC> (raw)

We have introduce a new return type vm_fault_t for
fault, page_mkwrite and pfn_mkwrite handlers. Update
the document for the same

Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
---
 Documentation/filesystems/Locking | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/filesystems/Locking b/Documentation/filesystems/Locking
index 2c39133..233413b 100644
--- a/Documentation/filesystems/Locking
+++ b/Documentation/filesystems/Locking
@@ -537,9 +537,9 @@ More details about quota locking can be found in fs/dquot.c.
 prototypes:
 	void (*open)(struct vm_area_struct*);
 	void (*close)(struct vm_area_struct*);
-	int (*fault)(struct vm_area_struct*, struct vm_fault *);
-	int (*page_mkwrite)(struct vm_area_struct *, struct vm_fault *);
-	int (*pfn_mkwrite)(struct vm_area_struct *, struct vm_fault *);
+	vm_fault_t (*fault)(struct vm_area_struct*, struct vm_fault *);
+	vm_fault_t (*page_mkwrite)(struct vm_area_struct *, struct vm_fault *);
+	vm_fault_t (*pfn_mkwrite)(struct vm_area_struct *, struct vm_fault *);
 	int (*access)(struct vm_area_struct *, unsigned long, void*, int, int);
 
 locking rules:
-- 
1.9.1


             reply	other threads:[~2018-07-22 12:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-22 13:01 Souptick Joarder [this message]
2018-07-22 13:01 ` [PATCH] mm: Introduce new type vm_fault_t Souptick Joarder
2018-07-23 15:42 ` Jonathan Corbet
2018-07-23 15:42   ` Jonathan Corbet

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=20180722130134.GA31321@jordon-HP-15-Notebook-PC \
    --to=jrdr.linux@gmail.com \
    --cc=ajitn.linux@gmail.com \
    --cc=brajeswar.linux@gmail.com \
    --cc=corbet@lwn.net \
    --cc=darrick.wong@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mszeredi@redhat.com \
    --cc=sabyasachi.linux@gmail.com \
    --cc=seanga2@gmail.com \
    --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 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.