From: Qais Yousef <qais.yousef@arm.com>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Patrick Bellasi <patrick.bellasi@matbug.net>
Subject: Re: [PATCH 1/5] Move sched_attr struct and syscall definitions into header file
Date: Sat, 23 Jan 2021 16:50:55 +0000 [thread overview]
Message-ID: <20210123165055.yphylpc575dqbw5s@e107158-lin> (raw)
In-Reply-To: <20210120102555.mu5czlpkb3gujapc@ws.net.home>
On 01/20/21 11:25, Karel Zak wrote:
> On Sat, Jan 16, 2021 at 07:09:36PM +0000, Qais Yousef wrote:
> > So that we can re-use them in other files.
>
> Good idea.
>
> > +++ b/include/sched_attr.h
> > @@ -0,0 +1,97 @@
> > +/*
> > + * This program is free software; you can redistribute it and/or modify
> > + * it under the terms of the GNU General Public License, version 2, as
> > + * published by the Free Software Foundation
>
> My goal is to keep include/ and lib/ usable for LGPL and BRD code,
> because util-linux is not only GPL code. The ideal solution is to
> use public domain or LGPL for this shared directories.
>
> Maybe we can use Public Domain also for this new header file as it
> contains only ifdef fallbacks.
>
> The other solution is to keep GPL sched_attr.h in schedutils/ directory.
Sorry I didn't realize the licensing constraint.
Don't we need Robert's Love permission to change the license? Making it Public
Domain makes sense. There's nothing special in here.
Thanks
--
Qais Yousef
next prev parent reply other threads:[~2021-01-23 16:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 19:09 [PATCH 0/5] Add a new uclampset utility Qais Yousef
2021-01-16 19:09 ` [PATCH 1/5] Move sched_attr struct and syscall definitions into header file Qais Yousef
2021-01-20 10:25 ` Karel Zak
2021-01-23 16:50 ` Qais Yousef [this message]
2021-01-16 19:09 ` [PATCH 2/5] Add uclampset schedutil Qais Yousef
2021-01-20 12:21 ` Karel Zak
2021-01-23 18:26 ` Qais Yousef
2021-01-16 19:09 ` [PATCH 3/5] uclampset: Add man page Qais Yousef
2021-01-20 12:22 ` Karel Zak
2021-01-23 18:36 ` Qais Yousef
2021-01-20 14:46 ` Vincent Guittot
2021-01-23 18:31 ` Qais Yousef
2021-01-25 8:26 ` Vincent Guittot
2021-01-26 15:08 ` Qais Yousef
2021-01-16 19:09 ` [PATCH 4/5] uclampset: Plump into the build system Qais Yousef
2021-01-16 19:09 ` [PATCH 5/5] uclampset: Plumb in bash-completion Qais Yousef
2021-01-18 13:06 ` [PATCH 0/5] Add a new uclampset utility 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=20210123165055.yphylpc575dqbw5s@e107158-lin \
--to=qais.yousef@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=kzak@redhat.com \
--cc=patrick.bellasi@matbug.net \
--cc=peterz@infradead.org \
--cc=util-linux@vger.kernel.org \
--cc=vincent.guittot@linaro.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).