From: Madadi Vineeth Reddy <vineethr@linux.ibm.com>
To: Benno Schulenberg <bensberg@telfort.nl>, util-linux@vger.kernel.org
Cc: Karel Zak <kzak@redhat.com>,
Madadi Vineeth Reddy <vineethr@linux.ibm.com>
Subject: Re: chrt from git segfaults
Date: Sat, 12 Jul 2025 21:59:23 +0530 [thread overview]
Message-ID: <7ed788ae-8bfc-4879-bdcb-6c7231f53b04@linux.ibm.com> (raw)
In-Reply-To: <25e238da-af73-42fa-ad18-8d9e77d33bab@telfort.nl>
On 10/07/25 13:41, Benno Schulenberg wrote:
>
> Op 09-07-2025 om 20:45 schreef Madadi Vineeth Reddy:
>> Could you spin off a patch to make sure the priority argument is
>> optional for policies that don’t need it, even when --pid is not used?
>
> No. You broke it, you fix it.
>
Sure, I’ll send a patch. Thanks.
Thanks,
Madadi Vineeth Reddy
>
> Benno
>
next prev parent reply other threads:[~2025-07-12 16:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 14:47 [PATCH 1/4 V2] chrt: with more than one argument, interpret first argument as priority Benno Schulenberg
2025-07-03 14:47 ` [PATCH 2/4 V2] chrt: do not try to interpret the --pid option itself as a PID Benno Schulenberg
2025-07-03 14:47 ` [PATCH 3/4 V2] chrt: simplify the other check for too few arguments Benno Schulenberg
2025-07-06 5:58 ` Madadi Vineeth Reddy
2025-07-06 9:10 ` Benno Schulenberg
2025-07-09 7:12 ` chrt from git segfaults Benno Schulenberg
2025-07-09 18:45 ` Madadi Vineeth Reddy
2025-07-10 8:11 ` Benno Schulenberg
2025-07-12 16:29 ` Madadi Vineeth Reddy [this message]
2025-07-14 11:32 ` Karel Zak
2025-07-15 5:29 ` Madadi Vineeth Reddy
2025-07-15 9:19 ` Benno Schulenberg
2025-07-16 8:16 ` Karel Zak
2025-07-03 14:47 ` [PATCH 4/4 V2] chrt: do not try to interpret any other option as a PID either Benno Schulenberg
2025-07-06 6:09 ` Madadi Vineeth Reddy
2025-07-14 11:28 ` Karel Zak
2025-07-15 5:33 ` Madadi Vineeth Reddy
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=7ed788ae-8bfc-4879-bdcb-6c7231f53b04@linux.ibm.com \
--to=vineethr@linux.ibm.com \
--cc=bensberg@telfort.nl \
--cc=kzak@redhat.com \
--cc=util-linux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).