Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3080801imu; Sun, 9 Dec 2018 16:54:06 -0800 (PST) X-Google-Smtp-Source: AFSGD/VBGPh02+qJenZjckCEUu6vnwnItgH598+yxwN5dW2XsIoMiLlFAoEJ0cNqej0601qZuXoI X-Received: by 2002:a63:374e:: with SMTP id g14mr9331234pgn.59.1544403246637; Sun, 09 Dec 2018 16:54:06 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544403246; cv=none; d=google.com; s=arc-20160816; b=CGmsU4l/nGldPZzHCggMnbgwlHyGzmBQjlw/ZzEsvEnPoHKgscGlXDHd9oOwfHpPM6 dscztWTaSezwbS5qWfy7GS5LIicF6qgliaLgdcQXZP9wqTvTFuK4GWc3UNFGPCbf9Sa0 NtlaUWPxGnfciOpO7IiFzb3vxLL3RVlj3njbteUJI1JHGozcjzzYaYMIvrSSnxFgQFnE jDygKuf+dLDXYntm9uZ9B7aJGP9QmGtE2FiNfg5bJBG7TfxOS9gch34LsuYoOOWEpeUN 0WL+8PMyBCjX2M7GTR1fo6F+RL9I8afacrh8x27/8mBIITnTHfe6qBG2vd2BLkm9U/PP GhBg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:from:subject:cc:to:message-id:date; bh=zSEqADIxWBAu+Bmt83M2mx4da3GmvcEozPuS04gDsoE=; b=qGwNELVMFB09bur5zxw9eXyyov2Qb/BPrPMFnMxRRchGt6ZT2F5fEVyPvarqf8HdsF B/q600W+/7MJ/Nu2t5TOIUaJa8g/VrwOfKvyL2fmNreZqlD/homY1Vj3jgzmZckNbylp 3urLRVyeq4KawrkTvcXjMqdDRel6nPD2Hxzxwvf+dSCwvWkVgk91EFlcJ2tKQe9b8TA0 P+ezIobLbGVxTsdKSTvsEl7amDEauZ27S7MDbw60BskwfwD7E0wMkvxhbQpWwgWpRgNB qniWVE4qPNy/vOBNY0elISVepPKKqurjqfq7vPZhO1nHuhqvjGLQjKYd6qBWoB71tVNX bDPg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 1si8739356plk.296.2018.12.09.16.53.51; Sun, 09 Dec 2018 16:54:06 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726466AbeLJAby (ORCPT + 99 others); Sun, 9 Dec 2018 19:31:54 -0500 Received: from shards.monkeyblade.net ([23.128.96.9]:53376 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726268AbeLJAby (ORCPT ); Sun, 9 Dec 2018 19:31:54 -0500 Received: from localhost (unknown [IPv6:2601:601:9f80:35cd::bf5]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id 7D088144C6CA8; Sun, 9 Dec 2018 16:31:53 -0800 (PST) Date: Sun, 09 Dec 2018 16:31:52 -0800 (PST) Message-Id: <20181209.163152.1641648923109797638.davem@davemloft.net> To: sd@queasysnail.net Cc: andrew@lunn.ch, hkallweit1@gmail.com, sfr@canb.auug.org.au, netdev@vger.kernel.org, linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, f.fainelli@gmail.com Subject: Re: linux-next: Signed-off-by missing for commits in the net-next tree From: David Miller In-Reply-To: <20181209232722.GA4425@bistromath.localdomain> References: <011f5be3-4bc1-2e64-0ddf-b43b8dbc4dcd@gmail.com> <20181209214907.GC21186@lunn.ch> <20181209232722.GA4425@bistromath.localdomain> X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Sun, 09 Dec 2018 16:31:53 -0800 (PST) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Sabrina Dubroca Date: Mon, 10 Dec 2018 00:27:22 +0100 > Maybe Stephen's script to detect those missing sign-offs could be run > as a commit/apply hook by David? This happens regularly, sometimes > dropping more than just a sign-off. Yeah, that would probably be a good idea, maybe something even on the git.kernel.org side that won't let me push if I'm sending commits that have this problem.