Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp2525968yba; Mon, 6 May 2019 07:30:23 -0700 (PDT) X-Google-Smtp-Source: APXvYqzUy9/c7DzBiiDrAg+iz9tiYe5gendBmnlc7eBNt8KsSz5YbUzgi69kOOOewfTgxXyJKkmA X-Received: by 2002:a17:902:4501:: with SMTP id m1mr31565547pld.302.1557153022998; Mon, 06 May 2019 07:30:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557153022; cv=none; d=google.com; s=arc-20160816; b=xWuVHTfOpdMqvnMGFZdXZEMTCC51kqE47Oo10HYQ5Gu7IEmqFUVQCQF0hiXMI69lLz HPxj2kTccnO7UJmarl1V9kkmI1ZNeuIh9eF8P1cVuJJvruDZfQkCGSHTvr29JX07aqhx EU6gh7tdwbAvXiwOsv3dEmX10najFwxPMfBnEl1K5pWxC+9H05CPwSe1SX3YC/XZeTyj XIrpvkh+rzShJg4vMT6Amu/xi5b9MIwx5VM9oQUY2SNn2HjTVMJ3vTzgbFQUuCHjaLPq 3O0oDfvOhWLg93OwhM6eHqDpGn4NiaggRFDoLT+akr+Bwg67/756s29ELkIPw+tSb6cc yrVA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature:dkim-filter; bh=eqLFB0nVFnZiNimHn82KIGN7U2ZgzKcawlpMijhfc9w=; b=a3kHoQuFzJiG90TCBc/T0vBMQCINcit5KAS4RlHmKzzMY6F0+wuFfR25Zj574ozgcB Go/BmHfiMJKsanzWUqctnIl2BY9Rvh7Q4q+wi11A5uJ6NqzL8vAePP3Qt2OhjMz9eLow 2S232Y3kPfjXTMbMVcmFzv89Tvwqtp1TixWEK7R3ly+LBVXIMvm/apg8WHWnHIbr9+QS zwbnCgCMYbDnqwjar+CPrQRgMxIh5267sJ1wHdt9n6n0vNBGemZ4bItx8gv+6TYKOMuv Bo3NSJn0PTUMKF9tbC4Y9FU/0kzYY3RI1SsO2nRBu0S8Py+xuFnCx6WKU8Czz5VSM+Ui +lug== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nifty.com header.s=dec2015msa header.b=XhpGpVKT; 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 e3si14497470pfn.164.2019.05.06.07.30.06; Mon, 06 May 2019 07:30:22 -0700 (PDT) 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; dkim=pass header.i=@nifty.com header.s=dec2015msa header.b=XhpGpVKT; 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 S1726220AbfEFO3O (ORCPT + 99 others); Mon, 6 May 2019 10:29:14 -0400 Received: from conssluserg-01.nifty.com ([210.131.2.80]:22796 "EHLO conssluserg-01.nifty.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725883AbfEFO3O (ORCPT ); Mon, 6 May 2019 10:29:14 -0400 Received: from mail-vs1-f52.google.com (mail-vs1-f52.google.com [209.85.217.52]) (authenticated) by conssluserg-01.nifty.com with ESMTP id x46ESsXM029567 for ; Mon, 6 May 2019 23:28:55 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-01.nifty.com x46ESsXM029567 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.com; s=dec2015msa; t=1557152935; bh=eqLFB0nVFnZiNimHn82KIGN7U2ZgzKcawlpMijhfc9w=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=XhpGpVKTClir5AxkSP7NnwHlzCdghMB4dNiu1+xGvHpE07nPSmbwmD1d2ynaoeOuB FahHzJzl8/gkBMAQiJ9HlPTZjYwZ/r2pUzr9+aaAiL1ACzqOS3KkfF56H34Nr1BC4y 322kyQ0SfRdiY+J31kxWHBYV/ybhHi/TSvsr73oieLL1Xlgj8/ip0fIln4yCqlcx+p VY6kPFU+PLyQ3w7QLHtVZ9jLKmbrL9Lqmli6uTbJeGowaqligirlscL9AZBW0cs084 q7bX8b937+hT3AodRM+O5sBL6ZWg/G7Bpc+wHmC+YK3ZNPKlMLthIyGryGKMTC7a+c b8OIF2SoI285A== X-Nifty-SrcIP: [209.85.217.52] Received: by mail-vs1-f52.google.com with SMTP id c24so1369101vsp.7 for ; Mon, 06 May 2019 07:28:55 -0700 (PDT) X-Gm-Message-State: APjAAAX4P+cz+EvAXtqCBuCMCcAP8Q5+LCqOcTuwMB4DNaqM1LSNOpOq YUw15v/WprMSoLG/f0Bs4Xnt4ND6qhZpS68kWE0= X-Received: by 2002:a67:fd89:: with SMTP id k9mr1073873vsq.54.1557152934032; Mon, 06 May 2019 07:28:54 -0700 (PDT) MIME-Version: 1.0 References: <20190323015227.245455-1-dianders@chromium.org> <20190416163034.3e642818ebf27ed6891c1981@linux-foundation.org> <20190418160651.40cb6a11186a6c6028e9d20d@linux-foundation.org> In-Reply-To: From: Masahiro Yamada Date: Mon, 6 May 2019 23:28:17 +0900 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] kdb: Get rid of broken attempt to print CCVERSION in kdb summary To: Daniel Thompson Cc: Douglas Anderson , Jason Wessel , Christophe Leroy , "Peter Zijlstra (Intel)" , Kees Cook , kgdb-bugreport@lists.sourceforge.net, Johannes Weiner , Linux Kernel Mailing List , "Gustavo A. R. Silva" , Nicholas Mc Guire , Andrew Morton , Joe Perches Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This patch is technically super easy, but shows how difficult to apply a single patch in a correct manner. The following showed up in today's linux-next, doubling "Signed-off-by: Douglas Anderson " This is obviously caused by the committer. Do we need some check script for maintainers before "git push" ? commit 51fee3389d71bfd281df02c55546a6103779e145 Author: Douglas Anderson AuthorDate: Fri Mar 22 18:52:27 2019 -0700 Commit: Daniel Thompson CommitDate: Thu May 2 14:55:07 2019 +0100 kdb: Get rid of broken attempt to print CCVERSION in kdb summary If you drop into kdb and type "summary", it prints out a line that says this: ccversion CCVERSION ...and I don't mean that it actually prints out the version of the C compiler. It literally prints out the string "CCVERSION". The version of the C Compiler is already printed at boot up and it doesn't seem useful to replicate this in kdb. Let's just delete it. We can also delete the bit of the Makefile that called the C compiler in an attempt to pass this into kdb. This will remove one extra call to the C compiler at Makefile parse time and (very slightly) speed up builds. Signed-off-by: Douglas Anderson Reviewed-by: Masahiro Yamada Signed-off-by: Douglas Anderson Signed-off-by: Daniel Thompson On Sat, Apr 20, 2019 at 3:24 AM Joe Perches wrote: > > On Fri, 2019-04-19 at 12:28 +0900, Masahiro Yamada wrote: > > Hi Joe, > > > > Can you detect redundant Cc: by checkpatch? > > > > Please see below in details. > > Thanks. > > Yes, but I'm not sure why it's useful or necessary. > git send-email using some scripts elides duplicate email addresses > --- > scripts/checkpatch.pl | 13 +++++++++++++ > 1 file changed, 13 insertions(+) > > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl > index 1c421ac42b07..bedec83cb797 100755 > --- a/scripts/checkpatch.pl > +++ b/scripts/checkpatch.pl > @@ -2688,6 +2688,19 @@ sub process { > $signatures{$sig_nospace} = 1; > } > > +# Check for a cc: line with another signature -by: by the same author > + if ($sig_nospace =~ /^cc:/) { > + my $sig_email = substr($sig_nospace, 3); > + foreach my $sig (sort keys %signatures) { > + next if ($sig =~ /^cc:/); > + $sig =~ s/^[^:]+://; > + if ($sig eq $sig_email) { > + WARN("BAD_SIGN_OFF", > + "Unnecessary CC: as there is another signature with the same name/email address\n" . $herecurr); > + } > + } > + } > + > # Check Co-developed-by: immediately followed by Signed-off-by: with same name and email > if ($sign_off =~ /^co-developed-by:$/i) { > if ($email eq $author) { > > -- Best Regards Masahiro Yamada