From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Chris Wilson" <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/mm: Use debugobject to track lifetimes (rev3)
Date: Thu, 12 Mar 2020 14:59:36 -0000 [thread overview]
Message-ID: <158402517681.4949.7069419910887330132@emeril.freedesktop.org> (raw)
In-Reply-To: <20200312103548.19962-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: drm/mm: Use debugobject to track lifetimes (rev3)
URL : https://patchwork.freedesktop.org/series/74638/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
c869cbdfdc9f drm/mm: Use debugobject to track lifetimes
-:301: WARNING:TYPO_SPELLING: 'compatiblity' may be misspelled - perhaps 'compatibility'?
#301: FILE: include/drm/drm_mm.h:278:
+/* stubs for external module compatiblity */
total: 0 errors, 1 warnings, 0 checks, 283 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:[~2020-03-12 14:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 10:35 [Intel-gfx] [PATCH] drm/mm: Use debugobject to track lifetimes Chris Wilson
2020-03-12 11:11 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for " Patchwork
2020-03-12 11:19 ` [Intel-gfx] [PATCH] " Chris Wilson
2020-03-12 12:10 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/mm: Use debugobject to track lifetimes (rev2) Patchwork
2020-03-12 12:19 ` [Intel-gfx] [PATCH] drm/mm: Use debugobject to track lifetimes Chris Wilson
2020-03-12 12:35 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/mm: Use debugobject to track lifetimes (rev2) Patchwork
2020-03-12 14:59 ` Patchwork [this message]
2020-03-12 15:15 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/mm: Use debugobject to track lifetimes (rev3) Patchwork
2020-03-12 21:23 ` [Intel-gfx] [PATCH] drm/mm: Use debugobject to track lifetimes kbuild test robot
2020-03-12 22:18 ` kbuild test robot
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=158402517681.4949.7069419910887330132@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--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;
as well as URLs for NNTP newsgroup(s).