From: Joe Perches <joe@perches.com>
To: Marcus Wolf <marcus.wolf@smarthome-wolf.de>,
Marcus Wolf <linux@wolf-entwicklungen.de>,
gregkh@linuxfoundation.org, dan.carpenter@oracle.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: pi433: Make rf69_set_dc_cut_off_frequency_intern static
Date: Sat, 02 Dec 2017 10:05:05 -0800 [thread overview]
Message-ID: <1512237905.6321.26.camel@perches.com> (raw)
In-Reply-To: <0b0afaef-aa5e-5b45-e570-8ce6a100225a@smarthome-wolf.de>
On Sat, 2017-12-02 at 19:15 +0200, Marcus Wolf wrote:
> Can you give me a hint, how to invoke the checkpatch.pl.
There are lots of ways.
I suggest reading the output of $ ./scripts/checkpatch.pl --help
For instance:
[ after the fact checking ]
$ git checkout -b <branch>
[ commit one or more changes ]
$ git format-patch -<count_of_commits> -o <directory>
$ ./scripts/checkpatch.pl <directory>/*
[ or pipe git diff output to checkpatch ]
$ git checkout -b <branch>
[ edit files and save changes ]
$ git diff --stat -p | ./scripts/checkpatch.pl
[ or run checkpatch on a particular commit ]
$ ./scripts/checkpatch -g <commit>
[ or run checkpatch.pl on a range of commits ]
$ ./scripts/checkpatch.pl -g <rev1..rev2>
prev parent reply other threads:[~2017-12-02 18:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-02 15:20 [PATCH] staging: pi433: Make rf69_set_dc_cut_off_frequency_intern static Marcus Wolf
2017-12-02 15:56 ` Greg KH
2017-12-02 16:01 ` Marcus Wolf
2017-12-02 16:10 ` Greg KH
2017-12-02 16:46 ` Joe Perches
2017-12-02 17:15 ` Marcus Wolf
2017-12-02 18:05 ` Joe Perches [this message]
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=1512237905.6321.26.camel@perches.com \
--to=joe@perches.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@wolf-entwicklungen.de \
--cc=marcus.wolf@smarthome-wolf.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