Received: by 10.223.176.5 with SMTP id f5csp2191672wra; Sun, 4 Feb 2018 23:06:03 -0800 (PST) X-Google-Smtp-Source: AH8x224Zww2kzdiUO3hAEmnPUW8yP3BB3ZKN99wKy3Ukp1XGI+vSyC7lzlGZy96pIWIgp6fo4xF8 X-Received: by 2002:a17:902:930a:: with SMTP id bc10-v6mr43537346plb.19.1517814363296; Sun, 04 Feb 2018 23:06:03 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517814363; cv=none; d=google.com; s=arc-20160816; b=qW+16dXt32i8qklt5Am5IE+lDvzRRXCQak0+Y/jJyGZfqhTTTPvWEP3dAq3amYwmQ4 fTEqUon5IX/90Nx2QgZUrdmwaL3jGw8WnjSrKHLUStUsEhYVMvGzo/BgicVSJV90Aazx gpGFpZmHaGMD01Ho4ivWs++UIuueQm0oy89a3T6PIiFwK+kqo30GilsVbxOQRFKRvH5+ bPZIi1ZQmOKaeyB7ReGA17TREW3Eu793BQ4z6Un8cgjKKRuqgPgGGeiMefQD9c4DV36G UX1ZSGAjSjnOFN2ExSUgxD3Ju5+aQzaHbJkahXHdBWh6EikiPvs60cbnGxO6eBwBTOxf ts5A== 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 :references:in-reply-to:mime-version:dkim-signature:dkim-filter :arc-authentication-results; bh=qkJfsV2wMQ0A74z/oW/OGtRX+Xs7Bg2/JU+RJH6/fT0=; b=PxN65ywe81bzQlLJQ6HgvjlrWGbwF2vKdeaF9Vx/FJ3jDIPnnuSavU+0DRphP5FMan R/pUARh3QflMRPL7+4YlL6tpnz8wdIyhfFcV76wgGdnzflXdutsq7k7gfaDBBLnyjIk9 2eVrQ5b0950QcYypO7CrKeUmIFwIvXtzZee1XaQPnPsaYJOlekWVUNXc9O+cOByzp6z5 D6KgsKKcdJjfjLETK2VU8NYIZb0XA3xuyFJfjvHF76o1+kwRfgQFWUM9MWBfX6tGh8xs HWcFksXI4TRjVl24XOgBwQbHCBO/6gpKRFmg+S66kiLVwEfrEpEtHDbhigtjufYhvzKI Uqwg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nifty.com header.s=dec2015msa header.b=CgMfj9Zm; 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 6-v6si6435458plb.379.2018.02.04.23.05.48; Sun, 04 Feb 2018 23:06:03 -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; dkim=pass header.i=@nifty.com header.s=dec2015msa header.b=CgMfj9Zm; 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 S1750935AbeBEHFC (ORCPT + 99 others); Mon, 5 Feb 2018 02:05:02 -0500 Received: from conssluserg-01.nifty.com ([210.131.2.80]:19287 "EHLO conssluserg-01.nifty.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751938AbeBEHEz (ORCPT ); Mon, 5 Feb 2018 02:04:55 -0500 Received: from mail-ua0-f182.google.com (mail-ua0-f182.google.com [209.85.217.182]) (authenticated) by conssluserg-01.nifty.com with ESMTP id w1574dLq027218; Mon, 5 Feb 2018 16:04:40 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-01.nifty.com w1574dLq027218 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.com; s=dec2015msa; t=1517814280; bh=qkJfsV2wMQ0A74z/oW/OGtRX+Xs7Bg2/JU+RJH6/fT0=; h=In-Reply-To:References:From:Date:Subject:To:Cc:From; b=CgMfj9Zm3xekaEU2GwoJ1AKI5y4CPVWk7ZEvwKvqs4PI2GAH48Y9XP3rfD9nKljKf WXagYFyoID6N6zOGqf3GKOiSz0r1GYRIwNycN/CIesg1U252sM6pJ4UrlVxwstuhsj +TG6SjHclNpJ9Fs2+E+T5v6+wdVScp2ZoCnvO6vV+qW1R20CWAzIqr5FX/97jtJHXN 94bHZqeE5LXMhbSk+rGWM21ESI6FDO+czp+CS/xhyo9tJl/yAQlOaDnVkohIvXvpWh 0AZ10ZqHBnq+q27KLPn54HTSXV3Opa/A8SsEFQ6LasLjn52rCw8ufHE1zAgYL0gjio XMrY2LvvkXWYg== X-Nifty-SrcIP: [209.85.217.182] Received: by mail-ua0-f182.google.com with SMTP id i5so18004966uai.10; Sun, 04 Feb 2018 23:04:40 -0800 (PST) X-Gm-Message-State: AKwxytc5OguA3sGA+brQwSCpzbr67fTPQjTPIx6U3wp+GDjNc4wEj6ZW m/zhYlplwp/YFLga9fteOvIxguXW+dS45e5R6P4= X-Received: by 10.176.83.76 with SMTP id y12mr44524009uay.109.1517814279116; Sun, 04 Feb 2018 23:04:39 -0800 (PST) MIME-Version: 1.0 Received: by 10.176.83.212 with HTTP; Sun, 4 Feb 2018 23:03:58 -0800 (PST) In-Reply-To: <1517812899.3118.372.camel@oracle.com> References: <1517812899.3118.372.camel@oracle.com> From: Masahiro Yamada Date: Mon, 5 Feb 2018 16:03:58 +0900 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v4 1/1] runchecks: Generalize make C={1,2} to support multiple checkers To: Knut Omang Cc: Linux Kernel Mailing List , Mauro Carvalho Chehab , Nicolas Palix , Linux Kbuild mailing list , =?UTF-8?B?SMOla29uIEJ1Z2dl?= , "open list:DOCUMENTATION" , Jonathan Corbet , Gilles Muller , Tom Saeger , Michal Marek , =?UTF-8?B?TWlja2HDq2wgU2FsYcO8bg==?= , "Paul E. McKenney" , Julia Lawall , John Haxby , =?UTF-8?B?w4VzbXVuZCDDmHN0dm9sZA==?= , Matthew Wilcox , "Levin, Alexander (Sasha Levin)" , cocci@systeme.lip6.fr, Andrew Morton 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 2018-02-05 15:41 GMT+09:00 Knut Omang : > On Fri, 2018-01-19 at 11:14 +0100, Knut Omang wrote: >> Add scripts/runchecks which has generic support for running >> checker tools in a convenient and user friendly way that >> the author hopes can contribute to rein in issues detected >> by these tools in a manageable and convenient way. >> >> scripts/runchecks provides the following basic functionality: >> >> * Makes it possible to selectively suppress output from individual >> checks on a per file or per subsystem basis. >> * Unifies output and suppression input from different tools >> by providing a single unified syntax and presentation for the >> underlying tools in the style of "scripts/checkpatch.pl --show-types". >> * Allows selective run of one, or more (or all) configured tools >> for each file. >> >> In the Makefile system, the sparse specific setup has been replaced >> by setup for runchecks. > > Hi all, > > - Anything more I can/need to do to bring this forward? > - Any quiet concerns? > > I realize it is a subsystem crossing change, Is it? Only Kbuild this is related to. > and a lot going on elsewhere, > nevertheless I believe this is a time saver in the slightly longer run, > as it allows automation of checking, even without a "perfect" > code base to begin with. > Sorry for the delay. I have not been able to find time to dive into the detail yet. (Actually, I tried to do that for v2 or v3, where Python code was so dirty, then consumed my time to figure out what the code was trying to do) I find my concern here: https://lkml.org/lkml/2018/1/5/497 Anyway, I will take a look again when I find some time. You do not need to take care of the detail until I request to do so. -- Best Regards Masahiro Yamada