From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v2,1/1] drm/i915/pxp: Add drm_dbgs for critical PXP events. (rev2)
Date: Wed, 11 Oct 2023 03:00:48 -0000 [thread overview]
Message-ID: <169699324833.26515.9854513883605469872@emeril.freedesktop.org> (raw)
In-Reply-To: <20230913225714.877627-1-alan.previn.teres.alexis@intel.com>
== Series Details ==
Series: series starting with [v2,1/1] drm/i915/pxp: Add drm_dbgs for critical PXP events. (rev2)
URL : https://patchwork.freedesktop.org/series/123656/
State : warning
== Summary ==
Error: dim checkpatch failed
afd41e939c6c drm/i915/pxp: Add drm_dbgs for critical PXP events.
-:93: WARNING:LONG_LINE: line length of 105 exceeds 100 columns
#93: FILE: drivers/gpu/drm/i915/pxp/intel_pxp_irq.c:43:
+ pxp->session_events |= PXP_TERMINATION_REQUEST | PXP_INVAL_REQUIRED | PXP_EVENT_TYPE_IRQ;
total: 0 errors, 1 warnings, 0 checks, 95 lines checked
next prev parent reply other threads:[~2023-10-11 3:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 22:57 [PATCH v2 1/1] drm/i915/pxp: Add drm_dbgs for critical PXP events Alan Previn
2023-09-13 22:57 ` [Intel-gfx] " Alan Previn
2023-09-14 1:20 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v2,1/1] " Patchwork
2023-09-14 1:35 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-09-14 22:03 ` [PATCH v2 1/1] " Balasubrawmanian, Vivaik
2023-09-15 17:30 ` [Intel-gfx] " Balasubrawmanian, Vivaik
2023-10-11 3:00 ` Patchwork [this message]
2023-10-11 3:14 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [v2,1/1] drm/i915/pxp: Add drm_dbgs for critical PXP events. (rev2) Patchwork
2023-10-11 16:56 ` [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=169699324833.26515.9854513883605469872@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=alan.previn.teres.alexis@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 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.