From: Matthew Wilcox <willy@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org
Subject: [GIT PULL] XArray for 6.6
Date: Fri, 8 Sep 2023 18:44:13 +0100 [thread overview]
Message-ID: <ZPtdbS6FTadc3LVA@casper.infradead.org> (raw)
I had to update the expiration on my signing key. I don't know if you
pay attention to that, or whether my attempts to get my updated expiration
date into the system were successful.
The following changes since commit f837f0a3c94882a29e38ff211a36c1c8a0f07804:
Merge tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux (2023-07-28 11:21:57 -0700)
are available in the Git repository at:
git://git.infradead.org/users/willy/xarray.git tags/xarray-6.6
for you to fetch changes up to 2a15de80dd0f7e04a823291aa9eb49c5294f56af:
idr: fix param name in idr_alloc_cyclic() doc (2023-09-05 19:01:38 -0400)
----------------------------------------------------------------
XArray/IDA updates for 6.6
- Fix a bug encountered by people using bittorrent where they'd get
NULL pointer dereferences on page cache lookups when using XFS
- Two documentation fixes
----------------------------------------------------------------
Ariel Marcovitch (1):
idr: fix param name in idr_alloc_cyclic() doc
Matthew Wilcox (Oracle) (1):
XArray: Do not return sibling entries from xa_load()
Philipp Stanner (1):
xarray: Document necessary flag in alloc functions
include/linux/xarray.h | 18 ++++++++++
lib/idr.c | 2 +-
lib/xarray.c | 8 ++++-
tools/testing/radix-tree/multiorder.c | 68 +++++++++++++++++++++++++++++++++--
4 files changed, 92 insertions(+), 4 deletions(-)
next reply other threads:[~2023-09-08 17:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 17:44 Matthew Wilcox [this message]
2023-09-09 4:57 ` Linus Torvalds
2023-09-09 5:05 ` 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=ZPtdbS6FTadc3LVA@casper.infradead.org \
--to=willy@infradead.org \
--cc=linux-fsdevel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox