All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cheng-Yang Chou <yphbchou0911@gmail.com>
To: sched-ext@lists.linux.dev
Cc: tj@kernel.org, void@manifault.com, arighi@nvidia.com,
	changwoo@igalia.com, jserv@ccns.ncku.edu.tw
Subject: Re: [PATCH v2 0/2] tools/sched_ext: Sync configuration with upstream
Date: Tue, 24 Feb 2026 11:04:38 +0800	[thread overview]
Message-ID: <aZ0VRpQ5KnpXjNcd@eric-acer> (raw)
In-Reply-To: <20260217072600.953197-1-yphbchou0911@gmail.com>

On Tue, Feb 17, 2026 at 03:25:58PM +0800, Cheng-Yang Chou wrote:
> This series synchronizes the sched-ext tool's Kconfig and README.md
> with the upstream scx repository.
> 
> Changes in v2:
> - Rebase v1 to fix application failure.
> - Remove duplicate Kconfig entries and non-user-selectable options.
> - Refactor Kconfig comments for a more professional tone.
> - Link to v1: https://lore.kernel.org/all/20260216110014.771335-1-yphbchou0911@gmail.com/
> 
> Thanks,
> -chengyang
> 
> ---
> 
> Cheng-Yang Chou (2):
>   tools/sched_ext: Sync README.md Kconfig with upstream scx
>   tools/sched_ext: Add Kconfig to sync with upstream
> 
>  tools/sched_ext/Kconfig   | 61 +++++++++++++++++++++++++++++++++++++++
>  tools/sched_ext/README.md |  6 ----
>  2 files changed, 61 insertions(+), 6 deletions(-)
>  create mode 100644 tools/sched_ext/Kconfig
> 
> -- 
> 2.48.1
>

Gentle, ping!

Thanks,
cheng-yang

  parent reply	other threads:[~2026-02-24  3:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-17  7:25 [PATCH v2 0/2] tools/sched_ext: Sync configuration with upstream Cheng-Yang Chou
2026-02-17  7:25 ` [PATCH v2 1/2] tools/sched_ext: Sync README.md Kconfig with upstream scx Cheng-Yang Chou
2026-02-17  7:26 ` [PATCH v2 2/2] tools/sched_ext: Add Kconfig to sync with upstream Cheng-Yang Chou
2026-02-24  3:04 ` Cheng-Yang Chou [this message]
2026-02-24 17:56 ` [PATCH v2 0/2] tools/sched_ext: Sync configuration " Tejun Heo

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=aZ0VRpQ5KnpXjNcd@eric-acer \
    --to=yphbchou0911@gmail.com \
    --cc=arighi@nvidia.com \
    --cc=changwoo@igalia.com \
    --cc=jserv@ccns.ncku.edu.tw \
    --cc=sched-ext@lists.linux.dev \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.