From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 222094] sched_setattr: bug in `ERRORS` section w.r.t. `attr.sched_flags contains a flag other than SCHED_FLAG_RESET_ON_FORK`
Date: Fri, 23 Oct 2026 19:27:53 +0000 [thread overview]
Message-ID: <bug-222094-11311-6inWen38Cw@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-222094-11311@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=222094
--- Comment #3 from Alejandro Colomar (alx@kernel.org) ---
Hi,
> Date: 2026-10-23 18:47:22+0000
> From: bugzilla-daemon@kernel.org
>
> https://bugzilla.kernel.org/show_bug.cgi?id=222094
>
> --- Comment #2 from Enji Cooper (yaneurabeya@gmail.com) ---
> Created attachment 311258
> --> https://bugzilla.kernel.org/attachment.cgi?id=311258&action=edit
> Patch
>
> I've honestly never submitted a patch to the Linux mailing lists. There are a
> lot of hoops to jump through in order to make a contribution... I'll try, but
> please bear with me (I'll probably get something wrong).
Sure! You're welcome to try. :-)
I've forwarded your patch to the mailing list in this email.
Have a lovely night!
Alex
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2026-10-23 19:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 15:31 [Bug 222094] New: sched_setattr: bug in `ERRORS` section w.r.t. `attr.sched_flags contains a flag other than SCHED_FLAG_RESET_ON_FORK` bugzilla-daemon
2026-10-10 18:08 ` [Bug 222094] " bugzilla-daemon
2026-10-23 18:47 ` bugzilla-daemon
2026-10-23 19:27 ` bugzilla-daemon [this message]
2026-10-23 19:27 ` bugzilla-daemon
[not found] <bug-222094-216477@https.bugzilla.kernel.org/>
[not found] ` <bug-222094-216477-AkltlLpJO7@https.bugzilla.kernel.org/>
[not found] ` <atu07uXukn8V_4YN@debian>
2026-10-23 19:31 ` Alejandro Colomar
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=bug-222094-11311-6inWen38Cw@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-man@vger.kernel.org \
/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.