From: Tejun Heo <tj@kernel.org>
To: David Vernet <void@manifault.com>,
Andrea Righi <arighi@nvidia.com>,
Changwoo Min <changwoo@igalia.com>
Cc: sched-ext@lists.linux.dev, Emil Tsalapatis <emil@etsalapatis.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHSET sched_ext/for-7.1] tools/sched_ext/include: Sync include files with scx repo
Date: Sat, 07 Mar 2026 22:49:34 -1000 [thread overview]
Message-ID: <c6fc19977481b75281c3aac84f6d1ed1@kernel.org> (raw)
In-Reply-To: <20260308024519.1980564-1-tj@kernel.org>
> Tejun Heo (6):
> tools/sched_ext/include: Remove dead sdt_task_defs.h guard from common.h
> tools/sched_ext/include: Sync bpf_arena_common.bpf.h with scx repo
> tools/sched_ext/include: Add missing helpers to common.bpf.h
> tools/sched_ext/include: Add __COMPAT_HAS_scx_bpf_select_cpu_and macro
> tools/sched_ext/include: Add libbpf version guard for assoc_struct_ops
> tools/sched_ext/include: Regenerate enum_defs.autogen.h
Applied 1-6 to sched_ext/for-7.1.
Thanks.
--
tejun
prev parent reply other threads:[~2026-03-08 8:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-08 2:45 [PATCHSET sched_ext/for-7.1] tools/sched_ext/include: Sync include files with scx repo Tejun Heo
2026-03-08 2:45 ` [PATCH 1/6] tools/sched_ext/include: Remove dead sdt_task_defs.h guard from common.h Tejun Heo
2026-03-08 2:45 ` [PATCH 2/6] tools/sched_ext/include: Sync bpf_arena_common.bpf.h with scx repo Tejun Heo
2026-03-08 2:45 ` [PATCH 3/6] tools/sched_ext/include: Add missing helpers to common.bpf.h Tejun Heo
2026-03-08 2:45 ` [PATCH 4/6] tools/sched_ext/include: Add __COMPAT_HAS_scx_bpf_select_cpu_and macro Tejun Heo
2026-03-08 2:45 ` [PATCH 5/6] tools/sched_ext/include: Add libbpf version guard for assoc_struct_ops Tejun Heo
2026-03-08 2:45 ` [PATCH 6/6] tools/sched_ext/include: Regenerate enum_defs.autogen.h Tejun Heo
2026-03-08 8:20 ` [PATCHSET sched_ext/for-7.1] tools/sched_ext/include: Sync include files with scx repo Andrea Righi
2026-03-08 8:49 ` Tejun Heo [this message]
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=c6fc19977481b75281c3aac84f6d1ed1@kernel.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=emil@etsalapatis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sched-ext@lists.linux.dev \
--cc=void@manifault.com \
/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