Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/5] drm/i915/gt: Always track callers to intel_rps_mark_interactive()
Date: Wed, 30 Oct 2019 11:06:44 -0000	[thread overview]
Message-ID: <20191030110644.8995.93804@emeril.freedesktop.org> (raw)
In-Reply-To: <20191030103827.2413-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: series starting with [1/5] drm/i915/gt: Always track callers to intel_rps_mark_interactive()
URL   : https://patchwork.freedesktop.org/series/68770/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
62347effd8e0 drm/i915/gt: Always track callers to intel_rps_mark_interactive()
-:11: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#11: 
<3>[    4.813326] intel_rps_mark_interactive:652 GEM_BUG_ON(!rps->power.interactive)

total: 0 errors, 1 warnings, 0 checks, 46 lines checked
ffbcda201db9 drm/i915/gt: Call intel_gt_sanitize() directly
1572a210a9a8 drm/i915/gem: Leave reloading kernel context on resume to GT
fbe8724a2f25 drm/i915/gt: Move user_forcewake application to GT
546534e93a37 drm/i915: Defer rc6 shutdown to suspend_late

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Chris Wilson" <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/5] drm/i915/gt: Always track callers to intel_rps_mark_interactive()
Date: Wed, 30 Oct 2019 11:06:44 -0000	[thread overview]
Message-ID: <20191030110644.8995.93804@emeril.freedesktop.org> (raw)
Message-ID: <20191030110644.xcL6FgDYHGp0T59s_HavtaOAxkkUS4xktkBqTqoYCZ8@z> (raw)
In-Reply-To: <20191030103827.2413-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: series starting with [1/5] drm/i915/gt: Always track callers to intel_rps_mark_interactive()
URL   : https://patchwork.freedesktop.org/series/68770/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
62347effd8e0 drm/i915/gt: Always track callers to intel_rps_mark_interactive()
-:11: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#11: 
<3>[    4.813326] intel_rps_mark_interactive:652 GEM_BUG_ON(!rps->power.interactive)

total: 0 errors, 1 warnings, 0 checks, 46 lines checked
ffbcda201db9 drm/i915/gt: Call intel_gt_sanitize() directly
1572a210a9a8 drm/i915/gem: Leave reloading kernel context on resume to GT
fbe8724a2f25 drm/i915/gt: Move user_forcewake application to GT
546534e93a37 drm/i915: Defer rc6 shutdown to suspend_late

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-10-30 11:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-30 10:38 [PATCH 1/5] drm/i915/gt: Always track callers to intel_rps_mark_interactive() Chris Wilson
2019-10-30 10:38 ` [Intel-gfx] " Chris Wilson
2019-10-30 10:38 ` [PATCH 2/5] drm/i915/gt: Call intel_gt_sanitize() directly Chris Wilson
2019-10-30 10:38   ` [Intel-gfx] " Chris Wilson
2019-11-01 14:04   ` Andi Shyti
2019-11-01 14:04     ` [Intel-gfx] " Andi Shyti
2019-10-30 10:38 ` [PATCH 3/5] drm/i915/gem: Leave reloading kernel context on resume to GT Chris Wilson
2019-10-30 10:38   ` [Intel-gfx] " Chris Wilson
2019-11-01 13:47   ` Andi Shyti
2019-11-01 13:47     ` [Intel-gfx] " Andi Shyti
2019-10-30 10:38 ` [PATCH 4/5] drm/i915/gt: Move user_forcewake application " Chris Wilson
2019-10-30 10:38   ` [Intel-gfx] " Chris Wilson
2019-11-01 13:42   ` Andi Shyti
2019-11-01 13:42     ` [Intel-gfx] " Andi Shyti
2019-10-30 10:38 ` [PATCH 5/5] drm/i915: Defer rc6 shutdown to suspend_late Chris Wilson
2019-10-30 10:38   ` [Intel-gfx] " Chris Wilson
2019-10-30 23:57   ` Andi Shyti
2019-10-30 23:57     ` [Intel-gfx] " Andi Shyti
2019-10-30 11:06 ` Patchwork [this message]
2019-10-30 11:06   ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/5] drm/i915/gt: Always track callers to intel_rps_mark_interactive() Patchwork
2019-10-30 11:30 ` ✓ Fi.CI.BAT: success " Patchwork
2019-10-30 11:30   ` [Intel-gfx] " Patchwork
2019-10-30 12:34 ` [PATCH 1/5] " Andi Shyti
2019-10-30 12:34   ` [Intel-gfx] " Andi Shyti
2019-10-31 11:55 ` ✓ Fi.CI.IGT: success for series starting with [1/5] " Patchwork
2019-10-31 11:55   ` [Intel-gfx] " Patchwork

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=20191030110644.8995.93804@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.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