1. 22 1月, 2020 2 次提交
    • P
      drm/i915: Make WARN* drm specific where uncore or stream ptr is available · a9f236d1
      Pankaj Bharadiya 提交于
      drm specific WARN* calls include device information in the
      backtrace, so we know what device the warnings originate from.
      
      Covert all the calls of WARN* with device specific drm_WARN*
      variants in functions where intel_uncore/i915_perf_stream  struct
      pointer is readily available.
      
      The conversion was done automatically with below coccinelle semantic
      patch. checkpatch errors/warnings are fixed manually.
      
      @@
      identifier func, T;
      @@
      func(...) {
      ...
      struct intel_uncore *T = ...;
      <...
      (
      -WARN(
      +drm_WARN(&T->i915->drm,
      ...)
      |
      -WARN_ON(
      +drm_WARN_ON(&T->i915->drm,
      ...)
      |
      -WARN_ONCE(
      +drm_WARN_ONCE(&T->i915->drm,
      ...)
      |
      -WARN_ON_ONCE(
      +drm_WARN_ON_ONCE(&T->i915->drm,
      ...)
      )
      ...>
      
      }
      
      @@
      identifier func, T;
      @@
      func(struct intel_uncore *T,...) {
      <...
      (
      -WARN(
      +drm_WARN(&T->i915->drm,
      ...)
      |
      -WARN_ON(
      +drm_WARN_ON(&T->i915->drm,
      ...)
      |
      -WARN_ONCE(
      +drm_WARN_ONCE(&T->i915->drm,
      ...)
      |
      -WARN_ON_ONCE(
      +drm_WARN_ON_ONCE(&T->i915->drm,
      ...)
      )
      ...>
      
      }
      
      @@
      identifier func, T;
      @@
      func(struct i915_perf_stream *T,...) {
      +struct drm_i915_private *i915 = T->perf->i915;
      <+...
      (
      -WARN(
      +drm_WARN(&i915->drm,
      ...)
      |
      -WARN_ON(
      +drm_WARN_ON(&i915->drm,
      ...)
      |
      -WARN_ONCE(
      +drm_WARN_ONCE(&i915->drm,
      ...)
      |
      -WARN_ON_ONCE(
      +drm_WARN_ON_ONCE(&i915->drm,
      ...)
      )
      ...+>
      
      }
      
      command: ls drivers/gpu/drm/i915/*.c | xargs spatch --sp-file <script> \
      					--linux-spacing --in-place
      Signed-off-by: NPankaj Bharadiya <pankaj.laxminarayan.bharadiya@intel.com>
      Signed-off-by: NJani Nikula <jani.nikula@intel.com>
      Link: https://patchwork.freedesktop.org/patch/msgid/20200115034455.17658-11-pankaj.laxminarayan.bharadiya@intel.com
      a9f236d1
    • P
      drm/i915: Make WARN* drm specific where drm_priv ptr is available · 48a1b8d4
      Pankaj Bharadiya 提交于
      drm specific WARN* calls include device information in the
      backtrace, so we know what device the warnings originate from.
      
      Covert all the calls of WARN* with device specific drm_WARN*
      variants in functions where drm_i915_private struct pointer is readily
      available.
      
      The conversion was done automatically with below coccinelle semantic
      patch. checkpatch errors/warnings are fixed manually.
      
      @rule1@
      identifier func, T;
      @@
      func(...) {
      ...
      struct drm_i915_private *T = ...;
      <+...
      (
      -WARN(
      +drm_WARN(&T->drm,
      ...)
      |
      -WARN_ON(
      +drm_WARN_ON(&T->drm,
      ...)
      |
      -WARN_ONCE(
      +drm_WARN_ONCE(&T->drm,
      ...)
      |
      -WARN_ON_ONCE(
      +drm_WARN_ON_ONCE(&T->drm,
      ...)
      )
      ...+>
      }
      
      @rule2@
      identifier func, T;
      @@
      func(struct drm_i915_private *T,...) {
      <+...
      (
      -WARN(
      +drm_WARN(&T->drm,
      ...)
      |
      -WARN_ON(
      +drm_WARN_ON(&T->drm,
      ...)
      |
      -WARN_ONCE(
      +drm_WARN_ONCE(&T->drm,
      ...)
      |
      -WARN_ON_ONCE(
      +drm_WARN_ON_ONCE(&T->drm,
      ...)
      )
      ...+>
      }
      
      command: ls drivers/gpu/drm/i915/*.c | xargs spatch --sp-file \
      			<script> --linux-spacing --in-place
      Signed-off-by: NPankaj Bharadiya <pankaj.laxminarayan.bharadiya@intel.com>
      Signed-off-by: NJani Nikula <jani.nikula@intel.com>
      Link: https://patchwork.freedesktop.org/patch/msgid/20200115034455.17658-10-pankaj.laxminarayan.bharadiya@intel.com
      48a1b8d4
  2. 10 1月, 2020 1 次提交
  3. 14 9月, 2019 2 次提交
  4. 10 8月, 2019 1 次提交
  5. 07 8月, 2019 3 次提交
  6. 03 8月, 2019 1 次提交
  7. 02 8月, 2019 2 次提交
  8. 12 7月, 2019 1 次提交
  9. 09 7月, 2019 1 次提交
  10. 07 7月, 2019 1 次提交
  11. 05 7月, 2019 1 次提交
  12. 04 7月, 2019 1 次提交
  13. 20 6月, 2019 6 次提交
  14. 14 6月, 2019 3 次提交
  15. 10 6月, 2019 1 次提交
  16. 08 5月, 2019 1 次提交
  17. 08 4月, 2019 1 次提交
  18. 03 4月, 2019 2 次提交
  19. 29 3月, 2019 1 次提交
  20. 27 3月, 2019 8 次提交