Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752931AbbFAOAr (ORCPT ); Mon, 1 Jun 2015 10:00:47 -0400 Received: from mail-wi0-f169.google.com ([209.85.212.169]:35870 "EHLO mail-wi0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751643AbbFAOAl (ORCPT ); Mon, 1 Jun 2015 10:00:41 -0400 From: Valentin Rothberg To: gregkh@linuxfoundation.org, stefan.hengelein@fau.de, andreas.ruprecht@fau.de, pebolle@tiscali.nl Cc: linux-kernel@vger.kernel.org, Valentin Rothberg Subject: [PATCH 0/2] checkkconfigsymbols.py: find relevant commits Date: Mon, 1 Jun 2015 16:00:18 +0200 Message-Id: <1433167220-12292-1-git-send-email-valentinrothberg@gmail.com> X-Mailer: git-send-email 2.1.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1364 Lines: 34 This patch series consists of two patches adding an option (--find) to find and display git commits that may cause a Kconfig symbol to be missing. This option is helpful when diffing two states of the tree (e.g. v4.0-v4.1-rc1) to get a set of relevant git commits without doing that manually (i.e., git log -G SYMBOL v4.0..v4.1-rc1). Note that this option only works with --diff enabled. Since --find prints additional information, the output is colored such that missing symbols are printed yellow, relevant commits red. The new output looks as follows (entries are separated with blank lines): $ checkkconfigsymbols.py --diff v4.0..v4.1-rc1 --find ARCH_EXYNOS5433 drivers/clk/samsung/Makefile 96bd6224f07b clk: samsung: exynos5433: Add clocks using common clock framework ARCH_MB86S7X drivers/clk/Makefile 1ccdd04f5365 clk: Add clock driver for mb86s7x Valentin Rothberg (2): checkkconfigsymbols.py: find relevant commits checkkconfigsymbols.py: colored output scripts/checkkconfigsymbols.py | 43 ++++++++++++++++++++++++++++++++++++++---- 1 file changed, 39 insertions(+), 4 deletions(-) -- 2.1.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/