From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lars Kurth Subject: Re: [PATCH 1/5] xen/arm: Introduce enable callback to enable a capabilities on each online CPU Date: Wed, 24 Jan 2018 17:05:32 +0000 Message-ID: <24B6C00C-5114-48D8-A21A-C7FE1E11328F@gmail.com> References: <20180116142337.24942-1-julien.grall@linaro.org> <20180116142337.24942-2-julien.grall@linaro.org> <3f287ea5-f122-b375-4d98-e33733516816@linaro.org> <7F2FA84A-2CBA-45EC-9073-7FC86205BE5A@gmail.com> Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Content-Type: multipart/mixed; boundary="===============4218876180508032089==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Sender: "Xen-devel" To: Julien Grall Cc: Stefano Stabellini , andre.przywara@linaro.org, xen-devel List-Id: xen-devel@lists.xenproject.org --===============4218876180508032089== Content-Type: multipart/alternative; boundary="Apple-Mail=_3E584181-A7C2-4ED2-8738-F20DFCD3344A" --Apple-Mail=_3E584181-A7C2-4ED2-8738-F20DFCD3344A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi Julien, > On 18 Jan 2018, at 10:56, Julien Grall = wrote: >=20 > On 17/01/18 14:31, Lars Kurth wrote: >> Hi Julien, >=20 > Hi Lars, >=20 ...=20 >> Normally this isn't a problem: only if we ever have to relicense the = code or if someone does code archeology >> When we relicensed the ACPI builder, it created all sorts of problems = as outlined in = https://www.slideshare.net/xen_com_mgr/ossa17-mixed-license-foss-projects = >>> Lastly, we do have quite a bit of code in Xen coming from Linux (or = other project). A lot of them are not listed in = README.source/CONTRIBUTING. But only mention in the commit message (not = necessarily with Signed-off-by tag). >> That is true: which is why I have started fixing these, whenever I = found them and moved such information to README.source. >>> So I am quite interested to know what is the normal procedure here. >> I think: >> * Doing this via Signed-off-by tag is sufficient for a one-off-import >> * I would prefer if people added import related info README.source = files (and also in the commit message) >> Does this make sense? >=20 > I think it makes sense. Do you expect to see the README.source = per-directory? Or one at top level? I think one somewhere at the top level of the ARM tree is sufficient. It = depends on how often you import code. It shouldn't block the series. = Just something to do at some point Lars --Apple-Mail=_3E584181-A7C2-4ED2-8738-F20DFCD3344A Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi = Julien,

On 18 Jan 2018, at 10:56, Julien Grall <julien.grall@linaro.org> wrote:

On 17/01/18 14:31, = Lars Kurth wrote:
Hi Julien,

Hi Lars,

... 
Normally this isn't a problem: only if we ever have to = relicense the code or if someone does code archeology
When = we relicensed the ACPI builder, it created all sorts of problems as = outlined in https://www.slideshare.net/xen_com_mgr/ossa17-mixed-license-fos= s-projects
Lastly, = we do have quite a bit of code in Xen coming from Linux (or other = project). A lot of them are not listed in README.source/CONTRIBUTING. = But only mention in the commit message (not necessarily with = Signed-off-by tag).
That is true: which is = why I have started fixing these, whenever I found them and moved such = information to README.source.
So I am quite interested to know what is the normal = procedure here.
I think:
* = Doing this via Signed-off-by tag is sufficient for a one-off-import
* I would prefer if people added import related info = README.source files (and also in the commit message)
Does = this make sense?

I think it makes = sense. Do you expect to see the README.source per-directory? Or one at = top level?

I think one somewhere at the top level of the ARM = tree is sufficient. It depends on how often you import code. It = shouldn't block the series. Just something to do at some = point
Lars

= --Apple-Mail=_3E584181-A7C2-4ED2-8738-F20DFCD3344A-- --===============4218876180508032089== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmcKaHR0cHM6Ly9saXN0 cy54ZW5wcm9qZWN0Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3hlbi1kZXZlbA== --===============4218876180508032089==--