From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: linux-usb@vger.kernel.org, willy@infradead.org
Subject: usb: mon: Change return type to vm_fault_t
Date: Sun, 15 Apr 2018 07:49:16 +0200 [thread overview]
Message-ID: <20180415054916.GB9734@kroah.com> (raw)
On Sun, Apr 15, 2018 at 12:36:02AM +0530, Souptick Joarder wrote:
> Use new return type vm_fault_t for fault handler
> in struct vm_operations_struct.
Why?
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-04-15 5:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-15 5:49 Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-04-16 14:44 usb: mon: Change return type to vm_fault_t Greg Kroah-Hartman
2018-04-16 13:55 Matthew Wilcox
2018-04-16 11:48 Souptick Joarder
2018-04-16 7:47 Greg Kroah-Hartman
2018-04-15 11:10 Matthew Wilcox
2018-04-14 19:06 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=20180415054916.GB9734@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jrdr.linux@gmail.com \
--cc=linux-usb@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 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).