This is an automated email from the git hooks/post-receive script.

unknown user pushed a change to branch fs-current in repository linux-next.

omits 7d124fbc39f1 Merge branch 'next-fixes' of https://git.kernel.org/pub/sc [...] omits 395305e046fc Merge branch 'vfs.fixes' of https://git.kernel.org/pub/scm [...] adds a5edf3550f42 perf subcmd: avoid crash in exclude_cmds when excludes is empty adds 7947ad15614c perf lock: Provide a host_env for session new new 20c9ccffccd6 perf maps: Ensure kmap is set up for all inserts new 5aca7966d2a7 Merge tag 'perf-tools-fixes-for-v6.17-2025-09-16' of git:/ [...] new 1b82c04e8d77 Merge branch 'vfs.fixes' of https://git.kernel.org/pub/scm [...] new 50b69abeaaea Merge branch 'next-fixes' of https://git.kernel.org/pub/sc [...] new 00e782110428 nfs4_setup_readdir(): insufficient locking for ->d_parent- [...] new 8d391956e878 Merge branch 'fixes' of https://git.kernel.org/pub/scm/lin [...]

This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:

* -- * -- B -- O -- O -- O (7d124fbc39f1) \ N -- N -- N refs/heads/fs-current (8d391956e878)

You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.

Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.

The 6 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.

Summary of changes: fs/nfs/nfs4proc.c | 2 ++ tools/lib/subcmd/help.c | 3 +++ tools/perf/builtin-lock.c | 7 ++++++- tools/perf/util/maps.c | 9 +++++---- 4 files changed, 16 insertions(+), 5 deletions(-)