From: Boaz Harrosh <boazh@netapp.com>
To: Dan Williams <dan.j.williams@intel.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-nvdimm <linux-nvdimm@lists.01.org>
Subject: [PATCH] dax: ->direct_access does not sleep anymore
Date: Mon, 26 Feb 2018 18:50:35 +0200 [thread overview]
Message-ID: <6a5a6353-2714-8eb6-2566-a4384a95db0b@netapp.com> (raw)
In Patch:
[7a862fb] brd: remove dax support
Dan Williams has removed the only might_sleep
implementation of ->direct_access.
So we no longer need to check for it.
CC: Dan Williams <dan.j.williams@intel.com>
Signed-off-by: Boaz Harrosh <boazh@netapp.com>
---
drivers/dax/super.c | 6 ------
1 file changed, 6 deletions(-)
diff --git a/drivers/dax/super.c b/drivers/dax/super.c
index 3ec8046..0a75550 100644
--- a/drivers/dax/super.c
+++ b/drivers/dax/super.c
@@ -236,12 +236,6 @@ long dax_direct_access(struct dax_device *dax_dev, pgoff_t pgoff, long nr_pages,
{
long avail;
- /*
- * The device driver is allowed to sleep, in order to make the
- * memory directly accessible.
- */
- might_sleep();
-
if (!dax_dev)
return -EOPNOTSUPP;
--
2.5.5
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: Boaz Harrosh <boazh@netapp.com>
To: Dan Williams <dan.j.williams@intel.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-nvdimm <linux-nvdimm@lists.01.org>
Subject: [PATCH] dax: ->direct_access does not sleep anymore
Date: Mon, 26 Feb 2018 18:50:35 +0200 [thread overview]
Message-ID: <6a5a6353-2714-8eb6-2566-a4384a95db0b@netapp.com> (raw)
In Patch:
[7a862fb] brd: remove dax support
Dan Williams has removed the only might_sleep
implementation of ->direct_access.
So we no longer need to check for it.
CC: Dan Williams <dan.j.williams@intel.com>
Signed-off-by: Boaz Harrosh <boazh@netapp.com>
---
drivers/dax/super.c | 6 ------
1 file changed, 6 deletions(-)
diff --git a/drivers/dax/super.c b/drivers/dax/super.c
index 3ec8046..0a75550 100644
--- a/drivers/dax/super.c
+++ b/drivers/dax/super.c
@@ -236,12 +236,6 @@ long dax_direct_access(struct dax_device *dax_dev, pgoff_t pgoff, long nr_pages,
{
long avail;
- /*
- * The device driver is allowed to sleep, in order to make the
- * memory directly accessible.
- */
- might_sleep();
-
if (!dax_dev)
return -EOPNOTSUPP;
--
2.5.5
next reply other threads:[~2018-02-26 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 16:50 Boaz Harrosh [this message]
2018-02-26 16:50 ` [PATCH] dax: ->direct_access does not sleep anymore Boaz Harrosh
2018-02-26 20:41 ` Dan Williams
2018-02-26 20:41 ` Dan Williams
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=6a5a6353-2714-8eb6-2566-a4384a95db0b@netapp.com \
--to=boazh@netapp.com \
--cc=dan.j.williams@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.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.