From: Valentin Rothberg <valentinrothberg@gmail.com>
To: gregkh@linuxfoundation.org, stefan.hengelein@fau.de,
andreas.ruprecht@fau.de, pebolle@tiscali.nl
Cc: linux-kernel@vger.kernel.org,
Valentin Rothberg <valentinrothberg@gmail.com>
Subject: [PATCH 0/2] checkkconfigsymbols.py: find relevant commits
Date: Mon, 1 Jun 2015 16:00:18 +0200 [thread overview]
Message-ID: <1433167220-12292-1-git-send-email-valentinrothberg@gmail.com> (raw)
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
next reply other threads:[~2015-06-01 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 14:00 Valentin Rothberg [this message]
2015-06-01 14:00 ` [PATCH 1/2] " Valentin Rothberg
2015-06-01 14:00 ` [PATCH 2/2] checkkconfigsymbols.py: colored output Valentin Rothberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1433167220-12292-1-git-send-email-valentinrothberg@gmail.com \
--to=valentinrothberg@gmail.com \
--cc=andreas.ruprecht@fau.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=stefan.hengelein@fau.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®