lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Mon,  1 Jun 2015 16:00:18 +0200
From:	Valentin Rothberg <valentinrothberg@...il.com>
To:	gregkh@...uxfoundation.org, stefan.hengelein@....de,
	andreas.ruprecht@....de, pebolle@...cali.nl
Cc:	linux-kernel@...r.kernel.org,
	Valentin Rothberg <valentinrothberg@...il.com>
Subject: [PATCH 0/2] checkkconfigsymbols.py: find relevant commits

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ