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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3EB3FC7618E for ; Fri, 21 Apr 2023 18:38:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232255AbjDUSi2 (ORCPT ); Fri, 21 Apr 2023 14:38:28 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48420 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231282AbjDUSi1 (ORCPT ); Fri, 21 Apr 2023 14:38:27 -0400 X-Greylist: delayed 366 seconds by postgrey-1.37 at lindbergh.monkeyblade.net; Fri, 21 Apr 2023 11:38:25 PDT Received: from out-56.mta1.migadu.com (out-56.mta1.migadu.com [IPv6:2001:41d0:203:375::38]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B595F1FFE for ; Fri, 21 Apr 2023 11:38:25 -0700 (PDT) MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1682101936; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=uqYeX2aBmdkBzAWr+UB3hayRraxOs8lPFg59w2CNeVo=; b=WJBeMck123/k/KlRkqace/tptWT6sToqwwkOZww3bMDPcmzdHWZdqtE8O5MAJgtNYFtER3 lbIBsZkDNvGg7OmiRCNyZ4kIag0Z9rFa4VnGYYTqwGu18kP/CY1SdP5+qKUZuj71owfEhb 0F/0SrxyEyhbcbQr4w/O8FYs1OHVgEY= Date: Fri, 21 Apr 2023 18:32:15 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: "Konstantin Ryabitsev" Message-ID: <4d4471f957af144d7a0f22a2147d90f9@linux.dev> Subject: Re: [PATCH RESEND v2 1/2] dt-bindings: display: simple: add support for InnoLux G070ACE-L01 To: "Krzysztof Kozlowski" , "Doug Anderson" Cc: richard.leitner@linux.dev, "Thierry Reding" , "Sam Ravnborg" , "David Airlie" , "Daniel Vetter" , "Rob Herring" , "Krzysztof Kozlowski" , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, "Richard Leitner" In-Reply-To: <2d7d8462-4e75-bbd2-4ae5-6403eda43020@linaro.org> References: <2d7d8462-4e75-bbd2-4ae5-6403eda43020@linaro.org> <20230201-innolux-g070ace-v2-0-2371e251dd40@skidata.com> <20230201-innolux-g070ace-v2-1-2371e251dd40@skidata.com> <184f0a80-34bc-5ebf-58bb-82a310eb91f6@linaro.org> X-Migadu-Flow: FLOW_OUT Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org April 21, 2023 1:01 PM, "Krzysztof Kozlowski" wrote:=0A>> Ah, got it. So I guess from the perspective of "b4" eve= ry time the=0A>> author modifies a patch (like adding new tags to it) the= n it's a new=0A>> application of Signed-off-by and thus the old Signed-of= f-by is removed=0A>> from the top and a new one is added below all the ta= gs that have been=0A>> received. Thus if b4 grabs all the tags off the ma= iling list for=0A>> applying it ends up in a different order than if it g= rabs all the tags=0A>> off the mailing list for sending a new version.=0A= >> =0A>> OK, I can understand that perspective. I'll keep it in mind.=0A>= =0A> Yeah. I actually agree with your point that submitter's SoB should= =0A> always be the last one, but I agree more with using process via=0A> = standardized tools. IOW, since I cannot change in this matter b4, I need= =0A> to agree with it. :)=0A=0AFWIW, everyone disagrees on how it should = be done (which is a totally normal state of things). B4 uses the "chain o= f custody" logic when it comes to trailers, described here:=0A=0Ahttps://= lore.kernel.org/tools/20221031165842.vxr4kp6h7qnkc53l@meerkat.local/=0A= =0AIn brief, the logic here is that the "Signed-off-by" trailer indicates= where the chain of custody for all previous trailers ends. The following= order:=0A=0AReviewed-by: Reviewer <>=0ASigned-off-by: Submitter <>=0ASig= ned-off-by: Submaintainer <>=0A=0ATells that it was the Submitter who col= lected and applied the Reviewed-by tag, which is why when someone runs "b= 4 trailers -u", their Signed-off-by is always moved to the bottom to indi= cate the proper chain of custody boundary.=0A=0AThe following order says = something very different:=0A=0ASigned-off-by: Submitter <>=0AReviewed-by:= Reviewer <>=0ASigned-off-by: Submaintainer <>=0A=0AThis indicates that t= he "Reviewed-by" trailer was collected by the Submaintainer, because it i= s below the chain-of-custody boundary of the Submitter.=0A=0AThe main rea= son is if Reviewer says "hey, I don't remember reviewing this, who put my= name in there," the order will point at the person in whose custody sect= ion this tag shows up.=0A=0AHope this helps.=0A=0ABest regards,=0A-K