From: Changwoo Min <changwoo@igalia.com>
To: Tejun Heo <tj@kernel.org>
Cc: void@manifault.com, arighi@nvidia.com, kernel-dev@igalia.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] sched_ext: Compatible testing of SCX_ENQ_CPU_SELECTED
Date: Sat, 8 Feb 2025 18:04:17 +0900 [thread overview]
Message-ID: <e67b4285-519f-4f4f-92e4-f8d4a6186414@igalia.com> (raw)
In-Reply-To: <Z6cSFmXvNkmI0qKv@slm.duckdns.org>
Hello,
Thanks for the quick review!
On 25. 2. 8. 17:13, Tejun Heo wrote:
> On Sat, Feb 08, 2025 at 01:43:28PM +0900, Changwoo Min wrote:
>> Changwoo Min (4):
>> sched_ext: Add enum_defs.autogen.h
>> sched_ext: Include enum_defs.autogen.h from common/common.bpf.h
>> sched_ext: Add __COMPAT_is_enq_cpu_selected() for BPF compatability
>> sched_ext: Use __COMPAT_is_enq_cpu_selected() in scx_qmap
>
> Can you collapse the four patches into a single patch? I don't think this
> needs to be split this granularly.
Sure, I will send out a collapsed version.
Regards,
Changwoo Min
prev parent reply other threads:[~2025-02-08 9:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 4:43 Changwoo Min
2025-02-08 4:43 ` [PATCH 1/4] sched_ext: Add enum_defs.autogen.h Changwoo Min
2025-02-08 4:43 ` [PATCH 2/4] sched_ext: Include enum_defs.autogen.h from common/common.bpf.h Changwoo Min
2025-02-08 4:43 ` [PATCH 3/4] sched_ext: Add __COMPAT_is_enq_cpu_selected() for BPF compatability Changwoo Min
2025-02-08 4:43 ` [PATCH 4/4] sched_ext: Use __COMPAT_is_enq_cpu_selected() in scx_qmap Changwoo Min
2025-02-08 8:13 ` [PATCH 0/4] sched_ext: Compatible testing of SCX_ENQ_CPU_SELECTED Tejun Heo
2025-02-08 9:04 ` Changwoo Min [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=e67b4285-519f-4f4f-92e4-f8d4a6186414@igalia.com \
--to=changwoo@igalia.com \
--cc=arighi@nvidia.com \
--cc=kernel-dev@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--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
all inboxes | Powered by JetHome®