From: Matthew Wilcox <willy@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: [GIT PULL] XArray fixes for 5.18
Date: Fri, 1 Apr 2022 15:11:54 +0100 [thread overview]
Message-ID: <YkcIKm6hb4jWf9dx@casper.infradead.org> (raw)
The following changes since commit 1f2cfdd349b7647f438c1e552dc1b983da86d830:
printk: Fix incorrect __user type in proc_dointvec_minmax_sysadmin() (2022-02-03 11:27:38 -0800)
are available in the Git repository at:
git://git.infradead.org/users/willy/xarray tags/xarray-5.18
for you to fetch changes up to 3ed4bb77156da0bc732847c8c9df92454c1fbeea:
XArray: Update the LRU list in xas_split() (2022-03-31 08:52:57 -0400)
----------------------------------------------------------------
XArray update for 5.18:
- Documentation update
- Fix test-suite build after move of bitmap.h
- Fix xas_create_range() when a large entry is already present
- Fix xas_split() of a shadow entry
----------------------------------------------------------------
Matthew Wilcox (Oracle) (4):
XArray: Document the locking requirement for the xa_state
XArray: Include bitmap.h from xarray.h
XArray: Fix xas_create_range() when multi-order entry present
XArray: Update the LRU list in xas_split()
Documentation/core-api/xarray.rst | 14 +++++++++-----
include/linux/xarray.h | 1 +
lib/test_xarray.c | 22 ++++++++++++++++++++++
lib/xarray.c | 4 ++++
4 files changed, 36 insertions(+), 5 deletions(-)
next reply other threads:[~2022-04-01 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 14:11 Matthew Wilcox [this message]
2022-04-01 21:45 ` [GIT PULL] XArray fixes for 5.18 pr-tracker-bot
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=YkcIKm6hb4jWf9dx@casper.infradead.org \
--to=willy@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.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.