From: Patchwork <patchwork@emeril.freedesktop.org>
To: Eric Wong <e@80x24.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for iommu/intel: quirk to disable DMAR for QM57 igfx
Date: Sun, 20 Jan 2019 18:12:55 -0000 [thread overview]
Message-ID: <20190120181255.5988.44348@emeril.freedesktop.org> (raw)
In-Reply-To: <20181227114948.ev4b3jte3ubsc5us@dcvr>
== Series Details ==
Series: iommu/intel: quirk to disable DMAR for QM57 igfx
URL : https://patchwork.freedesktop.org/series/55481/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
1620746a0d85 iommu/intel: quirk to disable DMAR for QM57 igfx
-:32: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#32:
cf. https://lore.kernel.org/lkml/154659116310.4596.13613897418163029789@jlahtine-desk.ger.corp.intel.com/
total: 0 errors, 1 warnings, 0 checks, 22 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-01-20 18:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-27 11:49 iommu_intel or i915 regression in 4.18, 4.19.12 and drm-tip Eric Wong
2019-01-02 9:42 ` Joonas Lahtinen
2019-01-04 1:06 ` Eric Wong
2019-01-04 8:39 ` Joonas Lahtinen
2019-01-18 12:17 ` [PATCH] iommu/intel: quirk to disable DMAR for QM57 igfx Eric Wong
2019-01-22 10:39 ` Joerg Roedel
2019-01-22 10:46 ` Daniel Vetter
2019-01-22 11:01 ` Joerg Roedel
2019-01-22 14:48 ` Joonas Lahtinen
2019-01-22 16:51 ` Joerg Roedel
2019-01-23 15:02 ` Joonas Lahtinen
2019-01-23 16:49 ` Joerg Roedel
2019-01-20 18:12 ` Patchwork [this message]
2019-01-20 18:30 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-01-20 20:46 ` ✓ 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=20190120181255.5988.44348@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=e@80x24.org \
--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