From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915: Attach the pci match data to the device upon creation
Date: Wed, 05 Sep 2018 14:25:52 -0000 [thread overview]
Message-ID: <20180905142552.5306.47292@emeril.freedesktop.org> (raw)
In-Reply-To: <20180905140921.17467-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [1/2] drm/i915: Attach the pci match data to the device upon creation
URL : https://patchwork.freedesktop.org/series/49187/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
418a878462ee drm/i915: Attach the pci match data to the device upon creation
-:84: WARNING:AVOID_BUG: Avoid crashing the kernel - try using WARN_ON & recovery code rather than BUG() or BUG_ON()
#84: FILE: drivers/gpu/drm/i915/i915_drv.c:1353:
+ BUG_ON(device_info->gen > sizeof(device_info->gen_mask) * BITS_PER_BYTE);
total: 0 errors, 1 warnings, 0 checks, 107 lines checked
4c81281ccea1 drm/i915: Move final cleanup of drm_i915_private to i915_driver_destroy
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-09-05 14:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 14:09 [PATCH 1/2] drm/i915: Attach the pci match data to the device upon creation Chris Wilson
2018-09-05 14:09 ` [PATCH 2/2] drm/i915: Move final cleanup of drm_i915_private to i915_driver_destroy Chris Wilson
2018-09-05 18:33 ` Michal Wajdeczko
2018-09-05 14:25 ` Patchwork [this message]
2018-09-05 14:43 ` ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915: Attach the pci match data to the device upon creation Patchwork
2018-09-05 19:11 ` ✓ 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=20180905142552.5306.47292@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