linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tobin C. Harding" <me@tobin.cc>
To: Joe Perches <joe@perches.com>
Cc: "Tobin C. Harding" <me@tobin.cc>,
	Andy Whitcroft <apw@canonical.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] checkpatch: warn for use of %px
Date: Wed,  6 Dec 2017 14:37:05 +1100	[thread overview]
Message-ID: <1512531428-3592-1-git-send-email-me@tobin.cc> (raw)

Patch 1 and 2 are cleanup patches. Each adds a new subroutine to remove
duplicate code.

Patch 3: Make checkpatch emit a warning for usage of specifier %px. 

The initial idea to emit the warning was given on LKML by Andrew Morton,
v1 requested permission to use 'Suggested-by' tag. This version does not
add that tag.

thanks,
Tobin.

v2:
 - change new sub name stat_real() -> get_stat_real()
 - add new sub get_stat_here()
 - (add new sub routines as separate patches)
 - add 'Acked-by' tag for Joe
 - remove 'Suggested-by' tag for Andrew Morton

Tobin C. Harding (3):
  checkpatch: add sub routine get_stat_real()
  checkpatch: add sub routine get_stat_here()
  checkpatch: warn for use of %px

 scripts/checkpatch.pl | 114 +++++++++++++++++++++++++-------------------------
 1 file changed, 58 insertions(+), 56 deletions(-)

-- 
2.7.4

             reply	other threads:[~2017-12-06  3:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06  3:37 Tobin C. Harding [this message]
2017-12-06  3:37 ` [PATCH v2 1/3] checkpatch: add sub routine get_stat_real() Tobin C. Harding
2017-12-06  3:37 ` [PATCH v2 2/3] checkpatch: add sub routine get_stat_here() Tobin C. Harding
2017-12-06  3:37 ` [PATCH v2 3/3] checkpatch: warn for use of %px Tobin C. Harding
2017-12-07 21:06   ` Tobin C. Harding
2017-12-07 21:15     ` Tobin C. Harding
2017-12-07 21:27       ` Joe Perches
2017-12-07 21:17     ` Joe Perches

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=1512531428-3592-1-git-send-email-me@tobin.cc \
    --to=me@tobin.cc \
    --cc=apw@canonical.com \
    --cc=joe@perches.com \
    --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;
as well as URLs for NNTP newsgroup(s).