[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 1/5] xen/arm: Introduce enable callback to enable a capabilities on each online CPU

Hi Julien,

On 18 Jan 2018, at 10:56, Julien Grall <julien.grall@xxxxxxxxxx> 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-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?

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

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.