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 snd/hda: Detangle unwind to avoid double release of display powerwell (rev2)
Date: Mon, 08 Apr 2019 12:22:36 -0000 [thread overview]
Message-ID: <20190408122236.21096.44239@emeril.freedesktop.org> (raw)
In-Reply-To: <20190408094337.8709-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: snd/hda: Detangle unwind to avoid double release of display powerwell (rev2)
URL : https://patchwork.freedesktop.org/series/59158/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
c354dafa354d snd/hda: Detangle unwind to avoid double release of display powerwell
-:8: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#8:
<4> [265.019680] WARNING: CPU: 1 PID: 163 at drivers/gpu/drm/i915/intel_runtime_pm.c:162 cancel_intel_runtime_pm_wakeref+0x87/0x160 [i915]
total: 0 errors, 1 warnings, 0 checks, 49 lines checked
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-04-08 12:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 9:43 [PATCH] snd/hda: Detangle unwind to avoid double release of display powerwell Chris Wilson
2019-04-08 10:54 ` ✗ Fi.CI.BAT: failure for " Patchwork
2019-04-08 10:56 ` [PATCH v2] " Chris Wilson
2019-04-08 12:22 ` Patchwork [this message]
2019-04-08 12:27 ` [PATCH] " kbuild test robot
2019-04-08 12:51 ` ✓ Fi.CI.BAT: success for snd/hda: Detangle unwind to avoid double release of display powerwell (rev2) Patchwork
2019-04-08 12:53 ` Chris Wilson
2019-04-08 15:02 ` ✓ Fi.CI.IGT: " 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=20190408122236.21096.44239@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.