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/icl: More workaround for port F detection due to broken VBTs
Date: Fri, 10 May 2019 14:36:13 -0000 [thread overview]
Message-ID: <20190510143613.17667.33240@emeril.freedesktop.org> (raw)
In-Reply-To: <20190510140255.25215-1-imre.deak@intel.com>
== Series Details ==
Series: drm/i915/icl: More workaround for port F detection due to broken VBTs
URL : https://patchwork.freedesktop.org/series/60508/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
28212f668a27 drm/i915/icl: More workaround for port F detection due to broken VBTs
-:11: WARNING:TYPO_SPELLING: 'existant' may be misspelled - perhaps 'existent'?
#11:
6 ports and/or get a VBT fix to mark these ports non-existant, but until
-:18: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#18:
WARN_ON(intel_wait_for_register(&dev_priv->uncore, regs->driver, (0x1 << ((pw_idx) * 2)), (0x1 << ((pw_idx) * 2)), 1))
total: 0 errors, 2 warnings, 0 checks, 16 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-05-10 14:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 14:02 [PATCH] drm/i915/icl: More workaround for port F detection due to broken VBTs Imre Deak
2019-05-10 14:36 ` Patchwork [this message]
2019-05-10 15:09 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-05-10 17:34 ` ✓ Fi.CI.IGT: " Patchwork
2019-05-14 10:55 ` Imre Deak
2019-05-13 12:47 ` [PATCH] " Kahola, Mika
2019-05-13 13:56 ` Jani Nikula
2019-05-13 14:05 ` Imre Deak
2019-05-14 7:51 ` Jani Nikula
2019-05-14 9:37 ` Imre Deak
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=20190510143613.17667.33240@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