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 B4D2BC4332F for ; Tue, 14 Nov 2023 02:45:55 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230355AbjKNCpP (ORCPT ); Mon, 13 Nov 2023 21:45:15 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33524 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229454AbjKNCpN (ORCPT ); Mon, 13 Nov 2023 21:45:13 -0500 Received: from gandalf.ozlabs.org (gandalf.ozlabs.org [150.107.74.76]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 00C29198; Mon, 13 Nov 2023 18:45:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canb.auug.org.au; s=201702; t=1699929908; bh=Gi8y97nQFqKGwgOJbbb6k7fZuwkjoq/Rvdu4DGIdq0Y=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=cnd7nFvJdvOa8NHLiAvKAAGPVxc4TY1BhFDJr4l2rXWH7Gx6/Tzbb1se3T4Ul4x64 OTlVX97R1KAWSqZvKePa4j5PDI4nSC6zVq4PCiWhQ/SgwY/Ow7hnw/1SATDYBDvmY0 S4YcklyQ4aiUhxQ7/FqUn32QjASdP/OCJ8NwsJHThB5bjgl+xI/1kJTGW8D9yFvsrS 3jrVTDALrt9C+YwMrm6/tU4N+usDR2WFXLSTUeG0s7xKVa4zlm10eIN/llZeRc4A9B aP2BcJkmF0/UEYVTy7SClXN9mCfwJ/ev0zh33myspE93xPPSr17DIS7xo/S1Vm5N0P BNWJmsp9yu/lQ== Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.ozlabs.org (Postfix) with ESMTPSA id 4STrHl3gCGz4wcH; Tue, 14 Nov 2023 13:45:07 +1100 (AEDT) Date: Tue, 14 Nov 2023 13:45:06 +1100 From: Stephen Rothwell To: Luben Tuikov Cc: Daniel Vetter , Intel Graphics , DRI , Linux Kernel Mailing List , Linux Next Mailing List Subject: Re: linux-next: Signed-off-by missing for commit in the drm-misc tree Message-ID: <20231114134506.2ba0de1f@canb.auug.org.au> In-Reply-To: <3c306310-04b3-4658-a197-4b2d22a88274@gmail.com> References: <20231114075501.61321c29@canb.auug.org.au> <19740d41-dd5a-47e4-b3e8-539b45bbd3e5@gmail.com> <3c306310-04b3-4658-a197-4b2d22a88274@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/vfjO+_ZRiq3XzHms7GsPcc9"; protocol="application/pgp-signature"; micalg=pgp-sha256 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --Sig_/vfjO+_ZRiq3XzHms7GsPcc9 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi Luben, On Mon, 13 Nov 2023 20:32:40 -0500 Luben Tuikov wrote: > > On 2023-11-13 20:08, Luben Tuikov wrote: > > On 2023-11-13 15:55, Stephen Rothwell wrote: =20 > >> Hi all, > >> > >> Commit > >> > >> 0da611a87021 ("dma-buf: add dma_fence_timestamp helper") > >> > >> is missing a Signed-off-by from its committer. > >> =20 > >=20 > > In order to merge the scheduler changes necessary for the Xe driver, th= ose changes > > were based on drm-tip, which included this change from drm-misc-fixes, = but which > > wasn't present in drm-misc-next. > >=20 > > I didn't want to create a merge conflict between drm-misc-next and drm-= misc-fixes, > > when pulling that change from drm-misc-next to drm-misc-fixes, so that = I can apply =20 >=20 > ... when pulling that change from from drm-misc-fixes into drm-misc-next,= so that I can apply... >=20 > > the Xe scheduler changes on top of drm-misc-next. =20 >=20 > The change in drm-misc-fixes is b83ce9cb4a465b. The latter is contained > in linus-master, and in drm-misc-fixes, while the former is in drm-misc-n= ext. > When we merge linus-master/drm-misc-fixes into drm-misc-next, or whicheve= r way > it happens, I'd like to avoid a merge conflict, but wanted to expedite th= e changes > for Xe. None of that is relevant ... if you commit a patch to a tree that will be in the linux kernel tree, you must add your Signed-off-by to the commit. --=20 Cheers, Stephen Rothwell --Sig_/vfjO+_ZRiq3XzHms7GsPcc9 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAmVS3zIACgkQAVBC80lX 0GwJtggAkD7+ISMdGhuawUsK8eHqoe6XD78rEGSbC5QjpkKyNnQejtovwRHAMibV pzhHOonfSs8uxfbU61N0SI6iLlnPVydhUUwHDYXk/RxRAVodVrVW/uWbkXS5Oxtv UbFigYw3Hcs5Vy6/p77YnFsgVXs8Ba09iIKd3uZgDZTX3K8pnN0RGyw343rInPR0 d9TFMjpn3hWzANScGffubmX4Wa4zeRcuz79o1Rk15G8G5KxSfema9AqWGnjircVn cqgR4poVpb4rAJVGy20ylEWVOiCjU/NY+zDFk8bACgzkGMCAJXxeF27pSwGi1fP/ VgGh82PauC3TcQJFsYQJd3bj2ZWBfg== =EZ5f -----END PGP SIGNATURE----- --Sig_/vfjO+_ZRiq3XzHms7GsPcc9--