From: Cheng-Yang Chou <yphbchou0911@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, sched-ext@lists.linux.dev,
Tejun Heo <tj@kernel.org>, David Vernet <void@manifault.com>,
Andrea Righi <arighi@nvidia.com>,
Changwoo Min <changwoo@igalia.com>,
Ching-Chun Huang <jserv@ccns.ncku.edu.tw>,
Chia-Ping Tsai <chia7712@gmail.com>
Subject: Re: [PATCH] man7, man2: document SCHED_EXT policy
Date: Thu, 23 Apr 2026 00:46:44 +0800 [thread overview]
Message-ID: <20260423003214.G1987@cchengyang.duckdns.org> (raw)
In-Reply-To: <aejvcpOKmAxCnJQV@devuan>
Hi Alejandro,
On Wed, Apr 22, 2026 at 06:02:49PM +0200, Alejandro Colomar wrote:
> What's the reason for this weird formatting of the source code? At this
> point I wonder if this was generated by AI.
>
> Please take into account 'CONTRIBUTING.d/ai'.
Okay, after reading the AI policy doc carefully, I've decided to drop
this patch. I used AI to help with the formatting since I'm not familiar
with the rules here.
I didn't realize this was strictly forbidden here, my apologies :/
Sorry for the noise, and thanks for your time!
--
Cheers,
Cheng-Yang
next prev parent reply other threads:[~2026-04-22 16:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-12 18:16 [PATCH] man7, man2: document SCHED_EXT policy Cheng-Yang Chou
2026-04-22 16:02 ` Alejandro Colomar
2026-04-22 16:13 ` Cheng-Yang Chou
2026-04-22 16:36 ` G. Branden Robinson
2026-04-22 16:59 ` Alejandro Colomar
2026-04-22 17:23 ` G. Branden Robinson
2026-04-22 18:08 ` Alejandro Colomar
2026-04-22 16:46 ` Cheng-Yang Chou [this message]
2026-04-22 17:04 ` Alejandro Colomar
2026-04-22 17:04 ` G. Branden Robinson
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=20260423003214.G1987@cchengyang.duckdns.org \
--to=yphbchou0911@gmail.com \
--cc=alx@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=chia7712@gmail.com \
--cc=jserv@ccns.ncku.edu.tw \
--cc=linux-man@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox