From: Todd Previte <tprevite@gmail.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
Damien Lespiau <damien.lespiau@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Enable 5.4Ghz (HBR2) link rate for Displayport 1.2-capable devices
Date: Fri, 17 Jan 2014 08:22:08 -0700 [thread overview]
Message-ID: <52D94AA0.5000505@gmail.com> (raw)
In-Reply-To: <878uuebuo7.fsf@intel.com>
On 1/17/2014 6:32 AM, Jani Nikula wrote:
> On Fri, 17 Jan 2014, Damien Lespiau <damien.lespiau@intel.com> wrote:
>> I see spaces instead of tabs. You can use the useful checkpatch.pl
>> script on patches to catch those pesky style issues (from within a linux
>> tree):
>>
>> $ ./scripts/checkpatch.pl 0001-drm-i915-Enable-5.4Ghz-HBR2-link-rate-for-Displaypor.patch
>>
>> [...]
>>
>> total: 6 errors, 9 warnings, 55 lines checked
> Should anyone find this useful, I have these to check branches in my
> local repos directly:
>
> alias checkpatch='/path/to/checkpatch.pl -q --emacs --strict'
>
> checkbranch()
> {
> local commit
> local range
>
> if [ -z "$1" ]; then
> range="origin..HEAD"
> elif [ -n "`echo $1 | grep '\.\.'`" ]; then
> range="$1"
> else
> range="$1..HEAD"
> fi
>
> for commit in `git rev-list --reverse $range`; do
> git --no-pager log --oneline -1 $commit
> git format-patch --stdout -1 $commit | checkpatch -
> done
> }
>
> Then I can do:
>
> Check local patches against origin:
> $ checkbranch
>
> Check local patches against drm-intel/drm-intel-nightly:
> $ checkbranch drm-intel/drm-intel-nightly
>
> Check a revision range:
> $ checkbranch commit1..commit2
>
> Do note that checkpatch is not the law. But it helps you get some of the
> little things straight.
>
>
> HTH,
> Jani.
>
>
>
Cool thanks Jani. I'll give that a try.
-T
next prev parent reply other threads:[~2014-01-17 15:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 3:06 [PATCH] drm/i915: Enable 5.4Ghz (HBR2) link rate for Displayport 1.2-capable devices Todd Previte
2014-01-17 6:30 ` Daniel Vetter
2014-01-17 14:58 ` Todd Previte
2014-01-17 15:08 ` Damien Lespiau
2014-01-17 15:22 ` Todd Previte
2014-01-17 11:55 ` Damien Lespiau
2014-01-17 13:32 ` Jani Nikula
2014-01-17 15:22 ` Todd Previte [this message]
2014-01-17 15:00 ` Todd Previte
2014-01-17 16:58 ` [PATCH V2] " Todd Previte
2014-01-17 16:58 ` [PATCH] " Todd Previte
2014-01-17 17:34 ` Daniel Vetter
2014-01-20 17:19 ` [PATCH v3] " Todd Previte
2014-01-20 17:19 ` Todd Previte
2014-01-21 9:26 ` Daniel Vetter
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=52D94AA0.5000505@gmail.com \
--to=tprevite@gmail.com \
--cc=damien.lespiau@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
/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