From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 7A69CC433EF for ; Fri, 26 Nov 2021 12:53:16 +0000 (UTC) Received: from list by lists.xenproject.org with outflank-mailman.232736.403569 (Exim 4.92) (envelope-from ) id 1mqaip-0001Qt-92; Fri, 26 Nov 2021 12:52:59 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 232736.403569; Fri, 26 Nov 2021 12:52:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mqaip-0001Qm-4c; Fri, 26 Nov 2021 12:52:59 +0000 Received: by outflank-mailman (input) for mailman id 232736; Fri, 26 Nov 2021 12:52:58 +0000 Received: from mail.xenproject.org ([104.130.215.37]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mqaio-0001QT-61 for xen-devel@lists.xenproject.org; Fri, 26 Nov 2021 12:52:58 +0000 Received: from xenbits.xenproject.org ([104.239.192.120]) by mail.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1mqaio-0007QW-4a for xen-devel@lists.xenproject.org; Fri, 26 Nov 2021 12:52:58 +0000 Received: from iwj (helo=mariner.uk.xensource.com) by xenbits.xenproject.org with local-bsmtp (Exim 4.92) (envelope-from ) id 1mqaio-0000zf-3w for xen-devel@lists.xenproject.org; Fri, 26 Nov 2021 12:52:58 +0000 Received: from iwj by mariner.uk.xensource.com with local (Exim 4.89) (envelope-from ) id 1mqaid-0002h4-54; Fri, 26 Nov 2021 12:52:47 +0000 X-BeenThere: xen-devel@lists.xenproject.org List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Precedence: list Sender: "Xen-devel" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=xenproject.org; s=20200302mail; h=References:In-Reply-To:Subject:Cc:To:Date :Message-ID:Content-Transfer-Encoding:Content-Type:MIME-Version:From; bh=RqM/9ScO8rVmTAdmCy1NUpnvL9qxmcdabTpHgOpAl/8=; b=1X8/SkDu+qvIz75LLOQxkLl8Cu jW4lKh8jodMKCz14bz+28BLZthIDlkEFW1YGCwkH2iGiqWrXgn+K7BwiYj57BoW3iLjjYPMczboyd kTSfwL5fG6WZ886by595eY61uEq6U0YEb6n5nWkX9rjQ5JYYUmoxBhhk7ru63Aj8jQR4=; From: Ian Jackson MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <24992.55453.893877.246946@mariner.uk.xensource.com> Date: Fri, 26 Nov 2021 12:52:45 +0000 To: Jan Beulich Cc: Julien Grall , Andrew Cooper , George Dunlap , Stefano Stabellini , Wei Liu , "xen-devel\@lists.xenproject.org" Subject: Re: [PATCH 1/7] xz: add fall-through comments to a switch statement In-Reply-To: References: <0ed245fa-58a7-a5f6-b82e-48f9ed0b6970@suse.com> <0c0e67f3-5e0a-f047-ca09-1cf078e6b094@suse.com> <71ef250c-be92-2b2f-0f07-ce32c17d8050@xen.org> <0b808ce0-23a2-65ae-dfb3-b167d5565b31@suse.com> <6bcd1555-ee0d-dd6d-55ca-0ca0e64c3623@xen.org> X-Mailer: VM 8.2.0b under 24.5.1 (i686-pc-linux-gnu) Jan Beulich writes ("Re: [PATCH 1/7] xz: add fall-through comments to a switch statement"): > On 26.11.2021 11:04, Julien Grall wrote: > > For this case, you provided some sort of an explanation but so far, I am > > still waiting for a link to confirm that the signed-off-by match the one > > on the ML. > > I haven't been able to easily find a mail archive holding this patch. I 100% agree with Julien on all points in this thread. Please can we keep the Linux S-o-b. Note that S-o-b is not a chain of *approval* (whose relevance to us is debateable) but but a chain of *custody and transmission* for copyright/licence/gdpr purposes. That latter chain is hightly relevant to us. All such S-o-b should be retained. Of course if you got the patch somewhere other than the Linux commit, then the chain of custody doesn't pass through the Linux commit. But in that case I expect you to be able to say where you got it. Instead, I suggest that, having established what the Linux commit is, it is far simpler for us all to regard the Linux commit as our immediate source for the patch, rather than some ML post which you are not, apparently, able to find. Ian.