All of lore.kernel.org
 help / color / mirror / Atom feed
From: Souptick Joarder <jrdr.linux@gmail.com>
To: alexander.shishkin@linux.intel.com
Cc: linux-kernel@vger.kernel.org, willy@infradead.org
Subject: [PATCH] hwtracing: intel_th: Change return type to vm_fault_t
Date: Tue, 17 Apr 2018 19:45:47 +0530	[thread overview]
Message-ID: <20180417141547.GA30799@jordon-HP-15-Notebook-PC> (raw)

Use new return type vm_fault_t for fault handler. For
now, this is just documenting that the function returns
a VM_FAULT value rather than an errno. Once all instances
are converted, vm_fault_t will become a distinct type.

Reference id -> 1c8f422059ae ("mm: change return type to
vm_fault_t")

Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
---
 drivers/hwtracing/intel_th/msu.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/hwtracing/intel_th/msu.c b/drivers/hwtracing/intel_th/msu.c
index dfb57ea..0ac84eb 100644
--- a/drivers/hwtracing/intel_th/msu.c
+++ b/drivers/hwtracing/intel_th/msu.c
@@ -1190,7 +1190,7 @@ static void msc_mmap_close(struct vm_area_struct *vma)
 	mutex_unlock(&msc->buf_mutex);
 }

-static int msc_mmap_fault(struct vm_fault *vmf)
+static vm_fault_t msc_mmap_fault(struct vm_fault *vmf)
 {
 	struct msc_iter *iter = vmf->vma->vm_file->private_data;
 	struct msc *msc = iter->msc;
--
1.9.1

             reply	other threads:[~2018-04-17 14:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-17 14:15 Souptick Joarder [this message]
2018-05-02  5:44 ` [PATCH] hwtracing: intel_th: Change return type to vm_fault_t Souptick Joarder
2018-05-02 13:58   ` Alexander Shishkin
     [not found]     ` <CAFqt6zbSuVZjH0W6o7fMLpytk28y_4tZ7Mt1B36SX=+LkaUP3A@mail.gmail.com>
     [not found]       ` <CAFqt6zbyCvknqkwnhQiyY1j32zufVk0rkPfxgKbytZcXY=xTVQ@mail.gmail.com>
2018-06-17  5:54         ` Souptick Joarder
2018-07-02 15:58 Souptick Joarder

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=20180417141547.GA30799@jordon-HP-15-Notebook-PC \
    --to=jrdr.linux@gmail.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --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.