From: Qais Yousef <qais.yousef@arm.com>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH v2 2/5] Add uclampset schedutil
Date: Tue, 2 Feb 2021 11:02:25 +0000 [thread overview]
Message-ID: <20210202110225.bhddyfcu43v34y7e@e107158-lin> (raw)
In-Reply-To: <20210202080131.lyvsda3rtp7btc3q@ws.net.home>
On 02/02/21 09:01, Karel Zak wrote:
> On Mon, Feb 01, 2021 at 05:32:02PM +0000, Qais Yousef wrote:
> > On 02/01/21 17:12, Karel Zak wrote:
> > > On Sat, Jan 30, 2021 at 08:50:36PM +0000, Qais Yousef wrote:
> > >
> > > Now I see that you have reused chrt concept of --pid. We keep it for
> > > chrt due to backward compatibility, but for new util it would be
> > > better to use standard 'required_argument' for --pid.
> >
> > Hmm what does required mean here? --pid is optional. But if passed, a value
> > is required to be passed indeed.
>
> It means a value required if --pid specified.
>
> > > > + static const struct option longopts[] = {
> > > > + { "all-tasks", no_argument, NULL, 'a' },
> > > > + { "pid", no_argument, NULL, 'p' },
> > >
> > > { "pid", required_argument, NULL, 'p' },
> >
> > Assuming this means --pid must be followed by a value then indeed that's what
> > we expect to happen.
>
> Yes.
>
> > will fix this and the 2 other occurrences below to include in v3.
>
> You don't have to send it to the mailing list, juts update your
> github repo and I'll merge it :-) Thanks.
Thanks a lot Karel. Pushed a new uclampset-v3 branch so that you can easily
review the diff against v2 before merging.
Cheers
--
Qais Yousef
next prev parent reply other threads:[~2021-02-02 11:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 20:50 [PATCH v2 0/5] Add a new uclampset utility Qais Yousef
2021-01-30 20:50 ` [PATCH v2 1/5] Move sched_attr struct and syscall definitions into header file Qais Yousef
2021-01-30 20:50 ` [PATCH v2 2/5] Add uclampset schedutil Qais Yousef
2021-02-01 16:12 ` Karel Zak
2021-02-01 17:32 ` Qais Yousef
2021-02-02 8:01 ` Karel Zak
2021-02-02 11:02 ` Qais Yousef [this message]
2021-02-02 15:40 ` Karel Zak
2021-02-02 16:29 ` Qais Yousef
2021-01-30 20:50 ` [PATCH v2 3/5] uclampset: Add man page Qais Yousef
2021-01-30 20:50 ` [PATCH v2 4/5] uclampset: Plump into the build system Qais Yousef
2021-01-30 20:50 ` [PATCH v2 5/5] uclampset: Plumb in bash-completion Qais Yousef
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=20210202110225.bhddyfcu43v34y7e@e107158-lin \
--to=qais.yousef@arm.com \
--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).