mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valentin Rothberg <valentinrothberg@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org,
	Valentin Rothberg <valentinrothberg@gmail.com>
Subject: [PATCH v2 0/5] checkkconfigsymbols: several updates
Date: Sun, 28 Aug 2016 08:51:27 +0200	[thread overview]
Message-ID: <20160828065132.74259-1-valentinrothberg@gmail.com> (raw)

Note that the patches base on [1], which has already been applied to
Greg's char-misc tree [2] (testing branch).

[1] https://lkml.org/lkml/2016/8/27/50
[2] git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git

Changelog v2:
- Break v1 into multiple changes (i.e., python3 port, ArgumentParser,
  pylint/pep8 warnings)
- More descriptive commit messages

Valentin Rothberg (5):
  checkkconfigsymbols.py: port to Python 3
  checkkconfigsymbols: use ArgumentParser
  checkkconfigsymbols.py: fix pylint and pep8 warnings
  checkkconfigsymblos: consistent symbol terminology
  checkkconfigsymbols: use arglist instead of cmd string

 scripts/checkkconfigsymbols.py | 338 ++++++++++++++++++++---------------------
 1 file changed, 169 insertions(+), 169 deletions(-)

-- 
2.9.3

             reply	other threads:[~2016-08-28  6:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-28  6:51 Valentin Rothberg [this message]
2016-08-28  6:51 ` [PATCH v2 1/5] checkkconfigsymbols.py: port to Python 3 Valentin Rothberg
2016-08-28  6:51 ` [PATCH v2 2/5] checkkconfigsymbols: use ArgumentParser Valentin Rothberg
2016-08-28  6:51 ` [PATCH v2 3/5] checkkconfigsymbols.py: fix pylint and pep8 warnings Valentin Rothberg
2016-08-28  6:51 ` [PATCH v2 4/5] checkkconfigsymblos: consistent symbol terminology Valentin Rothberg
2016-08-28  6:51 ` [PATCH v2 5/5] checkkconfigsymbols: use arglist instead of cmd string 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=20160828065132.74259-1-valentinrothberg@gmail.com \
    --to=valentinrothberg@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /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®