All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Cheng-Yang Chou <yphbchou0911@gmail.com>
Cc: linux-kernel@vger.kernel.org, void@manifault.com,
	arighi@nvidia.com, changwoo@igalia.com, jserv@ccns.ncku.edu.tw
Subject: Re: [PATCH 0/4] sched_ext: Standardize preprocessor comment markers
Date: Fri, 13 Jun 2025 14:42:06 -1000	[thread overview]
Message-ID: <aEzFXql93thUWWR3@slm.duckdns.org> (raw)
In-Reply-To: <20250611135404.13851-1-yphbchou0911@gmail.com>

On Wed, Jun 11, 2025 at 09:54:00PM +0800, Cheng-Yang Chou wrote:
> Cheng-Yang Chou (4):
>   sched_ext: Clean up and standardize #if/#else/#endif markers in
>     sched/ext.c
>   sched_ext: Clean up and standardize #if/#else/#endif markers in
>     sched/ext.h
>   sched_ext: Clean up and standardize #if/#else/#endif markers in
>     sched/ext_idle.c
>   sched_ext: Clean up and standardize #if/#else/#endif markers in
>     sched/ext_idle.h

Applied with subject line update. Patch 3 left a stray #else block causing a
build failure. Will post the updated patch as a reply to the patch. For this
sort of changes, please at least do build testing.

Thanks.

-- 
tejun

  parent reply	other threads:[~2025-06-14  0:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-11 13:54 [PATCH 0/4] sched_ext: Standardize preprocessor comment markers Cheng-Yang Chou
2025-06-11 13:54 ` [PATCH 1/4] sched_ext: Clean up and standardize #if/#else/#endif markers in sched/ext.c Cheng-Yang Chou
2025-06-11 13:54 ` [PATCH 2/4] sched_ext: Clean up and standardize #if/#else/#endif markers in sched/ext.h Cheng-Yang Chou
2025-06-11 13:54 ` [PATCH 3/4] sched_ext: Clean up and standardize #if/#else/#endif markers in sched/ext_idle.c Cheng-Yang Chou
2025-06-14  0:49   ` Tejun Heo
2025-06-11 13:54 ` [PATCH 4/4] sched_ext: Clean up and standardize #if/#else/#endif markers in sched/ext_idle.h Cheng-Yang Chou
2025-06-14  0:42 ` Tejun Heo [this message]
2025-06-14  8:06   ` [PATCH 0/4] sched_ext: Standardize preprocessor comment markers Cheng-Yang Chou

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=aEzFXql93thUWWR3@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=arighi@nvidia.com \
    --cc=changwoo@igalia.com \
    --cc=jserv@ccns.ncku.edu.tw \
    --cc=linux-kernel@vger.kernel.org \
    --cc=void@manifault.com \
    --cc=yphbchou0911@gmail.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.