From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Mauro Carvalho Chehab" <mchehab@kernel.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: don't flush TLB on GEN8 (rev2)
Date: Fri, 27 May 2022 09:49:09 -0000 [thread overview]
Message-ID: <165364494914.25503.15366575700529306709@emeril.freedesktop.org> (raw)
In-Reply-To: <b6417c5bf1b0ee8e093712264f325bd1268ed1e4.1653642514.git.mchehab@kernel.org>
== Series Details ==
Series: drm/i915: don't flush TLB on GEN8 (rev2)
URL : https://patchwork.freedesktop.org/series/104451/
State : warning
== Summary ==
Error: dim checkpatch failed
5a0ff8197012 drm/i915: don't flush TLB on GEN8
-:9: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#9:
http://gfx-ci.fi.intel.com/cibuglog-ng/issuefilterassoc/24297?query_key=42a999f48fa6ecce068bc8126c069be7c31153b4
-:55: WARNING:UNKNOWN_COMMIT_ID: Unknown commit id '494c2c9b630e', maybe rebased or not pulled?
#55:
Fixes: 494c2c9b630e ("drm/i915: Flush TLBs before releasing backing store")
total: 0 errors, 2 warnings, 0 checks, 12 lines checked
next prev parent reply other threads:[~2022-05-27 9:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 9:09 [PATCH] drm/i915: don't flush TLB on GEN8 Mauro Carvalho Chehab
2022-05-27 9:09 ` Mauro Carvalho Chehab
2022-05-27 9:09 ` [Intel-gfx] " Mauro Carvalho Chehab
2022-05-27 9:49 ` Patchwork [this message]
2022-05-27 10:55 ` Tvrtko Ursulin
2022-05-27 10:55 ` [Intel-gfx] " Tvrtko Ursulin
2022-05-27 10:55 ` Tvrtko Ursulin
2022-05-27 11:50 ` [Intel-gfx] " Mauro Carvalho Chehab
2022-05-27 11:50 ` Mauro Carvalho Chehab
2022-05-27 11:50 ` Mauro Carvalho Chehab
2022-05-27 12:09 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: don't flush TLB on GEN8 (rev2) Patchwork
2022-05-27 13:45 ` [Intel-gfx] ✓ 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=165364494914.25503.15366575700529306709@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mchehab@kernel.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.