[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 1/3] xen/arm: Sync sysregs and cpuinfo with Linux 5.18-rc3
- To: Stefano Stabellini <sstabellini@xxxxxxxxxx>
- From: Bertrand Marquis <Bertrand.Marquis@xxxxxxx>
- Date: Thu, 12 May 2022 12:34:16 +0000
- Accept-language: en-GB, en-US
- Arc-authentication-results: i=2; mx.microsoft.com 1; spf=pass (sender ip is 63.35.35.123) smtp.rcpttodomain=lists.xenproject.org smtp.mailfrom=arm.com; dmarc=pass (p=none sp=none pct=100) action=none header.from=arm.com; dkim=pass (signature was verified) header.d=armh.onmicrosoft.com; arc=pass (0 oda=1 ltdi=1 spf=[1,1,smtp.mailfrom=arm.com] dkim=[1,1,header.d=arm.com] dmarc=[1,1,header.from=arm.com])
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
- Arc-message-signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=F2Q/38xcpv8UQaVzBlDUMVAfUbm9EH+bnJFJB7hp5TQ=; b=l7HvUIHWNmaH4oa7Zh3tn6jloNUDO5VPUQQ7leyTpMHuPTj/19Q5cRARsjCxykA1SGwdPkl0Ni1DACmbANhOgSxXEOmo+vnRkBEEzp1WWa/jivvBp53BRbXdvBc7RTLe3DCZ0QLP9yvjU05uPeg49cmR854Lxso0UrE/FC5XCFMPGN0ym61atYPXMcXQ1WO97gsNEt/nHwprMDf7IRvkW49HIxVovBVvOwhNE5GqRCfDor6r1J2hh5BUdPTrnduzEPQLZOSEnAcEqh9Ft7RPTDJCL9ez46gODfwrxvj17d+gLh0QHP9ONF/SgVzBV0pRshLnyEwtoHbsHBJcHqowTw==
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=F2Q/38xcpv8UQaVzBlDUMVAfUbm9EH+bnJFJB7hp5TQ=; b=hD9GVjwGOo7bNw0BMMnDDCq/9WuxQhbKBB8hwLGPSgvtAPzVx6vR106HbR2uHJqKe/CuJcH3vT9GTE7d41x8pqCnCE4DDElu4Lx58FkL0jTkSE6kRlaYEnlSq2FWuZBZhL7kr6PcnjtrYkrzq9feMdrrrTiAcbpdZwXstItIjIlXHKlK/nTuE9KzzHS2/bh6BY2MZL7QPELrYHbdjA4eUuHps3bV4ho8Tk9Q0racDs6cKB3lCchXgkCD78GVbXTVHgm3/ypbc729peHTGKAjMO/H1hc1vSoQC6tT+FtXdKw6CrPKrJ6s4DfgMCnnrZvMQbgRKY4Uy6UJ4KUpZ5RUOA==
- Arc-seal: i=2; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=pass; b=ZO+oHt/giriSoPGBPV9OP3ab+1Is/bKiIgOuiRC6FMaTXDwNP2SenyW+3VqRB5+AV11goM3FjTaR90zEXzOzf6KQDGyXIjYO7Jd7tql45XmvuYhx/c7AirrEmnOjwJrkSkl5XMvbGnyCc26DHnTyAnMK5Rh4ZnEy9xZ+XZ31pF94T7rDdiW+LOxpEd8FBDICypXQF0fOxcPxPMcm/BcvNe9/l3EaUlV1Qplxb9rUW10/kWLy+E3DXYDHVP9iRiTQGi+IB/Km+dvhthksltdDs8X4oJiYkPKC6FlvwwBhW/pwteTiR12um2s2vBB8fJY7tuV0Pk21deodVSBvGFHQJA==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=JXwD+lfVHWF7nHPhyMcJd+739k6umkDmNvpWhkS3ZeFmtdxFd4eN6O39TnebyB6cRotnY/Y1jI6dNuK83Eau66nzqLQuEMpeHt1Ee9HZNNtSXG8A4f8ocU6uQFLatSoulJlMsEkeQRYnJcAqW6LEYryhY9cipkq1C6IJWRu+4O1jcbyYrM9Sdkev7LylPVmyAyzE3e/S5NvIeEmflzoNsTx0006hNNY2krX01e1xvSr40/n9Nqv9iNf0RHGrRub/t4bu1aV3qO/qJFzQMQrF6j0FvFsqowbU0Hq2yFrXSl+ofrX6ZzlrvqdMsai5LdcookUKM/FBr6C/r3JlZPU/Kg==
- Authentication-results-original: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=arm.com;
- Cc: Julien Grall <julien@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Volodymyr Babchuk <Volodymyr_Babchuk@xxxxxxxx>, George Dunlap <George.Dunlap@xxxxxxxxxx>
- Delivery-date: Thu, 12 May 2022 12:34:38 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
- Nodisclaimer: true
- Original-authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=arm.com;
- Thread-index: AQHYXtGhqgeBKorGIE+S3ZHm07cmGK0Nc+GAgADisYCAAAtXAIAAGQ0AgAAhcYCACMpfgIACZduAgAALAICAAAXAAIAAShgAgAEUEoA=
- Thread-topic: [PATCH 1/3] xen/arm: Sync sysregs and cpuinfo with Linux 5.18-rc3
Hi Stefano,
> On 11 May 2022, at 21:06, Stefano Stabellini <sstabellini@xxxxxxxxxx> wrote:
>
> On Wed, 11 May 2022, Bertrand Marquis wrote:
>>> I understand the patch is already written, so I was OK if you simply list
>>> of the commits with the authors/tags for this time.
>>
>> I would like to understand where this requirement is coming from.
>>
>> @George: is there some kind of legal reason for something like that ?
>
> I am not George but I'll answer the legal question. Our "legal" document
> is the DCO:
I agree with your analysis but I still think this is an area where we would
need the confirmation from George.
>
> https://developercertificate.org/
>
> This falls under case (b):
>
> (b) The contribution is based upon previous work that, to the best
> of my knowledge, is covered under an appropriate open source
> license and I have the right under that license to submit that
> work with modifications, whether created in whole or in part
> by me, under the same open source license (unless I am
> permitted to submit under a different license), as indicated
> in the file; or
>
> So from the legal point of view only your Signed-off-by line is
> required.
>
> I remember this well because I was confused about this a few years ago
> in another case of taking code from Linux.
>
>
>>> If both Stefano and you agree to not keep the authorships, then I will
>>> not stand against it. However, I will not get involved in
>>> committing and adding my ack.
>
> I am fine either way. My only request is to mention the Linux commit-id
> that Bertrand used as a base and Bertrand has already done that.
Ok
>
>
>> I want first to clear up this process and understand why you are
>> requesting this to know how I should do anything like that in the
>> future.
>
> It looks like our process docs are not very good on this point and might
> benefit from a clarification. I hope you are volunteering :-)
>
> Origin is defined as "it specifies the source of the patch" but it
> doesn't say what actually is considered a "source".
>
> I suggest to distinguish between the case where commits are ported
> individually from the case where code is copied over (like when we
> introduced SMMUv3.) If commits are copied individually, I think we
> probably want an Origin tag for each of them and the source is the
> original commit-id. If the code is copied from Linux (like the SMMUv3
> case) then we probably only want to request a single Origin tag (or a
> new tag?) with the base Linux version (5.18-rc3) rather than the
> commit-id being backported. In that case the source would be the
> repository baseline.
Before defining our own way to do that maybe we should check how
others are handling those cases to not reinvent the wheel.
Anybody has a suggestion of an other open source project we could
check which could have the same kind of “needs” ?
Cheers
Bertrand
>
> Cheers,
>
> Stefano
|