Received: by 2002:a05:6a10:c604:0:0:0:0 with SMTP id y4csp3378976pxt; Tue, 10 Aug 2021 02:08:24 -0700 (PDT) X-Google-Smtp-Source: ABdhPJywWWZa2J292o70JrUfj3o0WbW5nyUFwlrFBRnhW7zXghkaOHGW9foRZ5ElGAAfjUeO138U X-Received: by 2002:a05:6e02:4d2:: with SMTP id f18mr31249ils.21.1628586503563; Tue, 10 Aug 2021 02:08:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1628586503; cv=none; d=google.com; s=arc-20160816; b=RGwVZ4wAISysOv7ECWwu0g9hx9PiVb1h2e7HHFvqxYwVAfniVPXnz2lQV2riv7vUof MTaJiLGFOWnKodxlRE5q/dDmY7I/f047TANRfzML86vLnP5cKguAXwrm/S/21aPGngUM b/GwH7QvpiAbJMmtUQGgaH0wVZUBn/jBGswDUMzStmb9EDC5KcS1wVdBKTSVrKinLVRv nA2u/SGSeKCIiWzlF/SBDpjEQUfcQuc491rvAYJkiSX21t8uQdne9Z50csylH4Wk7iQh 0UxYqjQ0BHjgY2VNTh58H/oXAtVWv/g0HAwf4MPAGVWcfJx3HorE93J6eikSZWFkuPln TEZQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:mail-followup-to:message-id:subject:cc:to:from:date :dkim-signature; bh=GiCRq9oiIUoYtaK/RUZid1gDex+gXMLXotTaeNIUmiA=; b=rGDFKq5el3s7axk1JiOa/gwPJFwkmf3K1XskzGJ4YnKUOvAndDiIvCEOCiuFo5P53a 9v+ev9a+FXnUpOuKl8xK1ocn+yXa9T1HM6tAbIqBMRg2Q/1A61ppJzOEMMBOCMz/XR7L 86CW0YpjVAYjulxTh9wYVN8zwsK0MUvU+U1jMkpDqLrcXi4x64yfqA/9nFLEAlrEP/QF CMciURXxkQTIngpRBqMe/PsiU3rD3areXmXs9Sm9sQgKEAvVpbSEQrlqL/LWKio91oKB vvNIyLa+u4FaPVjR0CL0i1gfFbDzREUif8xbJ8PrhYDViSsKoyI70nyQqhTm6GPrA5Bv X/MA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ffwll.ch header.s=google header.b=TSLt8sQv; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id i12si2940512ilu.162.2021.08.10.02.08.11; Tue, 10 Aug 2021 02:08:23 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@ffwll.ch header.s=google header.b=TSLt8sQv; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237808AbhHJG1v (ORCPT + 99 others); Tue, 10 Aug 2021 02:27:51 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35562 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236653AbhHJG1u (ORCPT ); Tue, 10 Aug 2021 02:27:50 -0400 Received: from mail-wr1-x42d.google.com (mail-wr1-x42d.google.com [IPv6:2a00:1450:4864:20::42d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 32A69C0613D3 for ; Mon, 9 Aug 2021 23:27:29 -0700 (PDT) Received: by mail-wr1-x42d.google.com with SMTP id b13so24743312wrs.3 for ; Mon, 09 Aug 2021 23:27:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to; bh=GiCRq9oiIUoYtaK/RUZid1gDex+gXMLXotTaeNIUmiA=; b=TSLt8sQv3KMNzzPS3fSD/gdF+b63+EbUkwUJzjp0hhlGdZUZ7Rd/AoOvp0uJmLSyth idWsFEWNxLZHMkE7N0Us6P8gpIMwEjBGSYsiiNKmOb86eZDu77SO4PLc1ir83QOgXCk1 f5jZQSvinIlEibg/HrnX+nJfX9P07P/P7Zz7k= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to; bh=GiCRq9oiIUoYtaK/RUZid1gDex+gXMLXotTaeNIUmiA=; b=kWNr8oXX48H7NDzUXn+WWos4EHQLE4Fh445Avnl5jtb/mV71C/lwW7KFvPdpn42tRu sVA3WXCF+BqkrmhaUXxuD9R7leHJubZx2j1edf56kZRKuptS0hJJFb6QTfgunpm2W84j UO5/GYcm+KfxCa5wQo0NG2ksUJn7Lf2Fq6lAL9uahU04R9FNAg9rn+IqWlXHCUjcP0Q+ L0T2FOMsafr09F+iW0m9UQcNSwhUX/oVFP8A6p35yCLChMLFot0KVZmGRZKv3MP2VuEo JhmcMku84mBvf9FCGArBKmNbCB7veyQ0f7MkvKh47vu8bb6Uogls7cVxHMc0FuxzyOfv Etnw== X-Gm-Message-State: AOAM5321AxBEIEOoaNh+Pu/IDLWRzdQVgggIWN5uE3EEEOlyiR/p4cHy Gpmho+0TC8a0XuQd28Hdln575V8vAJvayg== X-Received: by 2002:a5d:6948:: with SMTP id r8mr15347886wrw.136.1628576847772; Mon, 09 Aug 2021 23:27:27 -0700 (PDT) Received: from phenom.ffwll.local ([2a02:168:57f4:0:efd0:b9e5:5ae6:c2fa]) by smtp.gmail.com with ESMTPSA id g16sm26620083wro.63.2021.08.09.23.27.26 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 09 Aug 2021 23:27:27 -0700 (PDT) Date: Tue, 10 Aug 2021 08:27:25 +0200 From: Daniel Vetter To: Matt Roper Cc: Joonas Lahtinen , DRI , Intel Graphics , Jani Nikula , Rodrigo Vivi , Stephen Rothwell , Linux Kernel Mailing List , Linux Next Mailing List Subject: Re: [Intel-gfx] linux-next: Signed-off-by missing for commit in the drm-intel tree Message-ID: Mail-Followup-To: Matt Roper , Joonas Lahtinen , DRI , Intel Graphics , Jani Nikula , Rodrigo Vivi , Stephen Rothwell , Linux Kernel Mailing List , Linux Next Mailing List References: <20210715141854.1ad4a956@canb.auug.org.au> <162823181614.15830.10618174106053255881@jlahtine-mobl.ger.corp.intel.com> <20210809161939.GS1556418@mdroper-desk1.amr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210809161939.GS1556418@mdroper-desk1.amr.corp.intel.com> X-Operating-System: Linux phenom 5.10.0-7-amd64 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Aug 09, 2021 at 09:19:39AM -0700, Matt Roper wrote: > On Mon, Aug 09, 2021 at 04:05:59PM +0200, Daniel Vetter wrote: > > On Fri, Aug 06, 2021 at 09:36:56AM +0300, Joonas Lahtinen wrote: > > > Hi Matt, > > > > > > Always use the dim tooling when applying patches, it will do the right > > > thing with regards to adding the S-o-b. > > > > fd.o server rejects any pushes that haven't been done by dim, so how did > > this get through? > > I definitely used dim for all of these patches, but I'm not sure how I > lost my s-o-b on this one. Maybe when I edited the commit message after > 'dim extract-tags' I accidentally deleted an extra line when I removed > the extract-tags marker? It's the only patch where the line is missing, > so it's almost certainly human error on my part rather than something > dim did wrong. Yeah that's an expected failure model, and dim is supposed to catch that by rechecking for sobs when you push. See dim_push_branch -> checkpatch_commit_push_range in dim. So you can hand-edit stuff however you want, dim /should/ catch it when pushing. That it didn't is kinda confusing and I'd like to know why that slipped through. > > Matt, can you pls figure out and type up the patch to > > plug that hole? > > Are you referring to a patch for dim here? The i915 patch has already > landed, so we can't change its commit message now. Yeah dim, not drm-intel, that can't be fixed anymore because it's all baked in. -Daniel > > > Matt > > > > > Thanks, Daniel > > > > > > > > Regards, Joonas > > > > > > Quoting Stephen Rothwell (2021-07-15 07:18:54) > > > > Hi all, > > > > > > > > Commit > > > > > > > > db47fe727e1f ("drm/i915/step: s/_revid_tbl/_revids") > > > > > > > > is missing a Signed-off-by from its committer. > > > > > > > > -- > > > > Cheers, > > > > Stephen Rothwell > > > > -- > > Daniel Vetter > > Software Engineer, Intel Corporation > > http://blog.ffwll.ch > > -- > Matt Roper > Graphics Software Engineer > VTT-OSGC Platform Enablement > Intel Corporation > (916) 356-2795 -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch