From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [git pull] vfs.git misc bits
Date: Fri, 24 Feb 2023 03:40:57 +0000 [thread overview]
Message-ID: <Y/gxyQA+yKJECwyp@ZenIV> (raw)
Assorted stuff that didn't fit anywhere else.
That should cover the rest of what I had in -next; I'd been sick for
several weeks, so a lot of pending stuff I hoped to put into -next
is going to miss this window ;-/
Al, off to deal with the remaining pile in the mailbox...
The following changes since commit b7bfaa761d760e72a969d116517eaa12e404c262:
Linux 6.2-rc3 (2023-01-08 11:49:43 -0600)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.misc
for you to fetch changes up to 39ecb653f671bbccd4a3c40f7f803f2874252f81:
nsfs: repair kernel-doc for ns_match() (2023-01-11 15:47:40 -0500)
----------------------------------------------------------------
Fabio M. De Francesco (1):
fs/cramfs: Convert kmap() to kmap_local_data()
Lukas Bulwahn (1):
nsfs: repair kernel-doc for ns_match()
Thomas Weißschuh (1):
nsfs: add compat ioctl handler
fs/cramfs/inode.c | 9 ++++-----
fs/nsfs.c | 3 ++-
2 files changed, 6 insertions(+), 6 deletions(-)
next reply other threads:[~2023-02-24 3:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 3:40 Al Viro [this message]
2023-02-25 3:33 ` [git pull] vfs.git misc bits Linus Torvalds
2023-02-25 3:45 ` Al Viro
2023-02-25 4:57 ` Al Viro
2023-02-25 17:04 ` Linus Torvalds
2023-02-25 18:11 ` Al Viro
[not found] ` <3805D9F9-FB5D-4A8A-BE4B-845DDC508441@gmail.com>
2023-02-25 22:02 ` Al Viro
2023-02-25 3:40 ` pr-tracker-bot
2023-02-25 3:40 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2017-09-14 23:03 Al Viro
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=Y/gxyQA+yKJECwyp@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).