From: Patchwork <patchwork@emeril.freedesktop.org>
To: Ville Syrjala <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for series starting with [v5,1/2] drm/i915: Make sandybridge_pcode_read() deal with the second data register (rev2)
Date: Sun, 26 May 2019 11:25:53 -0000 [thread overview]
Message-ID: <20190526112553.542.1797@emeril.freedesktop.org> (raw)
In-Reply-To: <20190521164025.30225-1-ville.syrjala@linux.intel.com>
== Series Details ==
Series: series starting with [v5,1/2] drm/i915: Make sandybridge_pcode_read() deal with the second data register (rev2)
URL : https://patchwork.freedesktop.org/series/60921/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
7c375533ea71 drm/i915: Make sandybridge_pcode_read() deal with the second data register
77c8f2cf64cc drm/i915: Make sure we have enough memory bandwidth on ICL
-:186: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#186:
new file mode 100644
-:404: WARNING:TYPO_SPELLING: 'succesfully' may be misspelled - perhaps 'successfully'?
#404: FILE: drivers/gpu/drm/i915/intel_bw.c:214:
+ /* Did we initialize the bw limits succesfully? */
total: 0 errors, 2 warnings, 0 checks, 675 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-26 11:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 16:40 [PATCH v5 1/2] drm/i915: Make sandybridge_pcode_read() deal with the second data register Ville Syrjala
2019-05-21 16:40 ` [PATCH v5 2/2] drm/i915: Make sure we have enough memory bandwidth on ICL Ville Syrjala
2019-05-24 15:36 ` [PATCH v6 " Ville Syrjala
2019-05-27 17:55 ` Ville Syrjälä
2019-05-21 18:16 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [v5,1/2] drm/i915: Make sandybridge_pcode_read() deal with the second data register Patchwork
2019-05-21 18:18 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-05-21 18:37 ` ✓ Fi.CI.BAT: success " Patchwork
2019-05-22 18:28 ` Ville Syrjälä
2019-05-22 13:15 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-05-26 11:25 ` Patchwork [this message]
2019-05-26 11:27 ` ✗ Fi.CI.SPARSE: warning for series starting with [v5,1/2] drm/i915: Make sandybridge_pcode_read() deal with the second data register (rev2) Patchwork
2019-05-26 11:42 ` ✓ Fi.CI.BAT: success " Patchwork
2019-05-26 20:09 ` ✓ 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=20190526112553.542.1797@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.com \
/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.