[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <b7f5fe8af0fe10a9aeabf4b48a7cf8c126676c24.camel@intel.com>
Date: Sat, 29 Dec 2018 19:52:56 +0000
From: "Williams, Dan J" <dan.j.williams@...el.com>
To: "torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>
Subject: [GIT PULL] dax fix for 4.21
Hi Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/dax-fix-4.21
...to receive a single fix for an issue you identified on the last dax
fix pull request. While I feel a bit silly sending a single-commit
pull-request there is nothing else queued up for dax this cycle. This
change has shipped in -next for multiple releases.
---
The following changes since commit 7566ec393f4161572ba6f11ad5171fd5d59b0fbd:
Linux 4.20-rc7 (2018-12-16 15:46:55 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/dax-fix-4.21
for you to fetch changes up to d8a706414af4827fc0b4b1c0c631c607351938b9:
dax: Use non-exclusive wait in wait_entry_unlocked() (2018-12-21 11:35:53 -0800)
----------------------------------------------------------------
dax fix 4.21
* Clean up unnecessary usage of prepare_to_wait_exclusive()
----------------------------------------------------------------
Dan Williams (1):
dax: Use non-exclusive wait in wait_entry_unlocked()
fs/dax.c | 16 +++++++---------
1 file changed, 7 insertions(+), 9 deletions(-)
Powered by blists - more mailing lists