From: Patchwork <patchwork@emeril.freedesktop.org>
To: Imre Deak <imre.deak@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Ensure minimum CDCLK requirement for audio
Date: Mon, 18 Mar 2019 18:01:41 -0000 [thread overview]
Message-ID: <20190318180141.20492.31545@emeril.freedesktop.org> (raw)
In-Reply-To: <20190318143435.1686-1-imre.deak@intel.com>
== Series Details ==
Series: drm/i915: Ensure minimum CDCLK requirement for audio
URL : https://patchwork.freedesktop.org/series/58132/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
f5ea7a63eeb3 drm/i915: Force 2*96 MHz cdclk on glk/cnl when audio power is enabled
-:60: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#60: FILE: drivers/gpu/drm/i915/intel_audio.c:745:
+static void glk_force_audio_cdclk(struct drm_i915_private *dev_priv,
+ bool enable)
total: 0 errors, 0 warnings, 1 checks, 212 lines checked
e871b62f8db1 drm/i915: Skip modeset for cdclk changes if possible
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-03-18 18:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 14:34 [PATCH v6 0/2] drm/i915: Ensure minimum CDCLK requirement for audio Imre Deak
2019-03-18 14:34 ` [PATCH v6 1/2] drm/i915: Force 2*96 MHz cdclk on glk/cnl when audio power is enabled Imre Deak
2019-03-18 14:34 ` [PATCH v6 2/2] drm/i915: Skip modeset for cdclk changes if possible Imre Deak
2019-03-18 18:37 ` Ville Syrjälä
2019-03-18 19:16 ` Imre Deak
2019-03-18 18:01 ` Patchwork [this message]
2019-03-18 18:03 ` ✗ Fi.CI.SPARSE: warning for drm/i915: Ensure minimum CDCLK requirement for audio Patchwork
2019-03-18 18:20 ` ✓ Fi.CI.BAT: success " Patchwork
2019-03-19 2:56 ` ✗ Fi.CI.IGT: failure " 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=20190318180141.20492.31545@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=imre.deak@intel.com \
--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