From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ian Rogers <irogers@google.com>, Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH 04/11] tools headers: Sync UAPI linux/fs.h with kernel sources
Date: Mon, 22 Dec 2025 14:57:09 -0800 [thread overview]
Message-ID: <20251222225716.3565649-4-namhyung@kernel.org> (raw)
In-Reply-To: <20251222225716.3565649-1-namhyung@kernel.org>
To pick up changes from:
b30ffcdc0c15a88f ("block: introduce BLKREPORTZONESV2 ioctl")
0d8627cc936de8ea ("blktrace: add definitions for blk_user_trace_setup2")
This should be used to beautify ioctl syscall arguments and it addresses
these tools/perf build warnings:
Warning: Kernel ABI header differences:
diff -u tools/perf/trace/beauty/include/uapi/linux/fs.h include/uapi/linux/fs.h
Please see tools/include/README.kernel-copies.
Cc: linux-fsdevel@vger.kernel.org
Signed-off-by: Namhyung Kim <namhyung@kernel.org>
---
tools/perf/trace/beauty/include/uapi/linux/fs.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/perf/trace/beauty/include/uapi/linux/fs.h b/tools/perf/trace/beauty/include/uapi/linux/fs.h
index beb4c2d1e41cb1bb..66ca526cf786c761 100644
--- a/tools/perf/trace/beauty/include/uapi/linux/fs.h
+++ b/tools/perf/trace/beauty/include/uapi/linux/fs.h
@@ -298,8 +298,9 @@ struct file_attr {
#define BLKROTATIONAL _IO(0x12,126)
#define BLKZEROOUT _IO(0x12,127)
#define BLKGETDISKSEQ _IOR(0x12,128,__u64)
-/* 130-136 are used by zoned block device ioctls (uapi/linux/blkzoned.h) */
+/* 130-136 and 142 are used by zoned block device ioctls (uapi/linux/blkzoned.h) */
/* 137-141 are used by blk-crypto ioctls (uapi/linux/blk-crypto.h) */
+#define BLKTRACESETUP2 _IOWR(0x12, 142, struct blk_user_trace_setup2)
#define BMAP_IOCTL 1 /* obsolete - kept for compatibility */
#define FIBMAP _IO(0x00,1) /* bmap access */
--
2.52.0.351.gbe84eed79e-goog
next prev parent reply other threads:[~2025-12-22 22:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 22:57 [PATCH 01/11] tools headers: Sync UAPI drm/drm.h " Namhyung Kim
2025-12-22 22:57 ` [PATCH 02/11] tools headers: Sync UAPI KVM headers " Namhyung Kim
2025-12-22 22:57 ` [PATCH 03/11] tools headers: Sync UAPI linux/fcntl.h " Namhyung Kim
2025-12-22 22:57 ` Namhyung Kim [this message]
2025-12-22 22:57 ` [PATCH 05/11] tools headers: Sync UAPI linux/mount.h " Namhyung Kim
2025-12-22 22:57 ` [PATCH 06/11] tools headers: Sync UAPI sound/asound.h " Namhyung Kim
2025-12-22 22:57 ` [PATCH 07/11] tools headers: Sync x86 headers " Namhyung Kim
2025-12-22 22:57 ` [PATCH 08/11] tools headers: Sync arm64 " Namhyung Kim
2025-12-23 15:36 ` Leo Yan
2025-12-23 18:11 ` Namhyung Kim
2025-12-22 22:57 ` [PATCH 09/11] tools headers: Sync linux/gfp_types.h " Namhyung Kim
2025-12-23 1:00 ` SeongJae Park
2025-12-23 18:06 ` Namhyung Kim
2025-12-22 22:57 ` [PATCH 10/11] tools headers: Sync linux/socket.h " Namhyung Kim
2025-12-22 22:57 ` [PATCH 11/11] tools headers: Sync syscall table " Namhyung Kim
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=20251222225716.3565649-4-namhyung@kernel.org \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®