From: Christian Brauner <brauner@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] vfs iomap updates
Date: Tue, 7 Nov 2023 11:18:34 +0100 [thread overview]
Message-ID: <20231107-vfs-iomap-60b485c2b4fb@brauner> (raw)
Hey Linus,
/* Summary */
As discussed on list last week this makes fs/iomap part of vfs.git with
Darrick as main reviewer.
/* Testing */
clang: Debian clang version 16.0.6 (16)
gcc: gcc (Debian 13.2.0-5) 13.2.0
All patches are based on v6.6 and have been sitting in linux-next.
No build failures or warnings were observed.
/* Conflicts */
At the time of creating this PR no merge conflicts were reported from
linux-next and no merge conflicts showed up doing a test-merge with
current mainline.
The following changes since commit ffc253263a1375a65fa6c9f62a893e9767fbebfa:
Linux 6.6 (2023-10-29 16:31:08 -1000)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.7.iomap
for you to fetch changes up to 64bc7eee421fafc5d491d65bff74f46430fe61af:
iomap: rename iomap entry (2023-11-07 10:52:08 +0100)
Please consider pulling these changes from the signed vfs-6.7.iomap tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.7.iomap
----------------------------------------------------------------
Christian Brauner (1):
iomap: rename iomap entry
Darrick J. Wong (1):
iomap: rotate maintainers
MAINTAINERS | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
next reply other threads:[~2023-11-07 10:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 10:18 Christian Brauner [this message]
2023-11-07 20:34 ` [GIT PULL] vfs iomap updates 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=20231107-vfs-iomap-60b485c2b4fb@brauner \
--to=brauner@kernel.org \
--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).