All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Pankaj Bharadiya" <pankaj.laxminarayan.bharadiya@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Introduce drm scaling filter property (rev8)
Date: Mon, 12 Oct 2020 20:54:32 -0000	[thread overview]
Message-ID: <160253607220.31908.1335597437219994573@emeril.freedesktop.org> (raw)
In-Reply-To: <20201012184130.937-1-pankaj.laxminarayan.bharadiya@intel.com>

== Series Details ==

Series: Introduce drm scaling filter property (rev8)
URL   : https://patchwork.freedesktop.org/series/73883/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
db97d091f394 drm: Introduce plane and CRTC scaling filter properties
ac9e547c61eb drm/drm-kms.rst: Add plane and CRTC scaling filter property documentation
e5508cf65017 drm/i915: Introduce scaling filter related registers and bit fields
-:71: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'id' - possible side-effects?
#71: FILE: drivers/gpu/drm/i915/i915_reg.h:7503:
+#define CNL_PS_COEF_INDEX_SET(pipe, id, set)  _MMIO_PIPE(pipe,    \
+			_ID(id, _PS_COEF_SET0_INDEX_1A, _PS_COEF_SET0_INDEX_2A) + (set) * 8, \
+			_ID(id, _PS_COEF_SET0_INDEX_1B, _PS_COEF_SET0_INDEX_2B) + (set) * 8)

-:71: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'set' - possible side-effects?
#71: FILE: drivers/gpu/drm/i915/i915_reg.h:7503:
+#define CNL_PS_COEF_INDEX_SET(pipe, id, set)  _MMIO_PIPE(pipe,    \
+			_ID(id, _PS_COEF_SET0_INDEX_1A, _PS_COEF_SET0_INDEX_2A) + (set) * 8, \
+			_ID(id, _PS_COEF_SET0_INDEX_1B, _PS_COEF_SET0_INDEX_2B) + (set) * 8)

-:75: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'id' - possible side-effects?
#75: FILE: drivers/gpu/drm/i915/i915_reg.h:7507:
+#define CNL_PS_COEF_DATA_SET(pipe, id, set)  _MMIO_PIPE(pipe,     \
+			_ID(id, _PS_COEF_SET0_DATA_1A, _PS_COEF_SET0_DATA_2A) + (set) * 8, \
+			_ID(id, _PS_COEF_SET0_DATA_1B, _PS_COEF_SET0_DATA_2B) + (set) * 8)

-:75: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'set' - possible side-effects?
#75: FILE: drivers/gpu/drm/i915/i915_reg.h:7507:
+#define CNL_PS_COEF_DATA_SET(pipe, id, set)  _MMIO_PIPE(pipe,     \
+			_ID(id, _PS_COEF_SET0_DATA_1A, _PS_COEF_SET0_DATA_2A) + (set) * 8, \
+			_ID(id, _PS_COEF_SET0_DATA_1B, _PS_COEF_SET0_DATA_2B) + (set) * 8)

total: 0 errors, 0 warnings, 4 checks, 47 lines checked
dbeefdcbdca3 drm/i915/display: Add Nearest-neighbor based integer scaling support
697e0b84d6e2 drm/i915: Enable scaling filter for plane and CRTC
-:96: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#96: FILE: drivers/gpu/drm/i915/display/intel_display.c:17076:
+		drm_crtc_create_scaling_filter_property(&crtc->base,
+						BIT(DRM_SCALING_FILTER_DEFAULT) |

-:156: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#156: FILE: drivers/gpu/drm/i915/display/intel_sprite.c:3216:
+		drm_plane_create_scaling_filter_property(&plane->base,
+						BIT(DRM_SCALING_FILTER_DEFAULT) |

total: 0 errors, 0 warnings, 2 checks, 104 lines checked


_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2020-10-12 20:54 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-12 18:41 [PATCH v6 0/5] Introduce drm scaling filter property Pankaj Bharadiya
2020-10-12 18:41 ` [Intel-gfx] " Pankaj Bharadiya
2020-10-12 18:41 ` [PATCH v6 1/5] drm: Introduce plane and CRTC scaling filter properties Pankaj Bharadiya
2020-10-12 18:41   ` [Intel-gfx] " Pankaj Bharadiya
2020-10-13 12:01   ` Simon Ser
2020-10-13 12:01     ` [Intel-gfx] " Simon Ser
2020-10-13 12:03   ` Simon Ser
2020-10-13 12:03     ` [Intel-gfx] " Simon Ser
2020-10-12 18:41 ` [PATCH v6 2/5] drm/drm-kms.rst: Add plane and CRTC scaling filter property documentation Pankaj Bharadiya
2020-10-12 18:41   ` [Intel-gfx] " Pankaj Bharadiya
2020-10-12 18:41 ` [PATCH v6 3/5] drm/i915: Introduce scaling filter related registers and bit fields Pankaj Bharadiya
2020-10-12 18:41   ` [Intel-gfx] " Pankaj Bharadiya
2020-10-12 18:41 ` [PATCH v6 4/5] drm/i915/display: Add Nearest-neighbor based integer scaling support Pankaj Bharadiya
2020-10-12 18:41   ` [Intel-gfx] " Pankaj Bharadiya
2020-10-20 15:02   ` Ville Syrjälä
2020-10-20 15:02     ` [Intel-gfx] " Ville Syrjälä
2020-10-12 18:41 ` [PATCH v6 5/5] drm/i915: Enable scaling filter for plane and CRTC Pankaj Bharadiya
2020-10-12 18:41   ` [Intel-gfx] " Pankaj Bharadiya
2020-10-12 20:54 ` Patchwork [this message]
2020-10-12 20:56 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Introduce drm scaling filter property (rev8) Patchwork
2020-10-12 21:19 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-10-13  2:32 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-10-20  8:25   ` Laxminarayan Bharadiya, Pankaj
2020-10-20 16:26     ` Vudum, Lakshminarayana
2020-10-13 14:26 ` [PATCH v6 0/5] Introduce drm scaling filter property Simon Ser
2020-10-13 14:26   ` [Intel-gfx] " Simon Ser
2020-10-20 13:33   ` Simon Ser
2020-10-20 13:33     ` [Intel-gfx] " Simon Ser
2020-10-20 16:21 ` [Intel-gfx] ✓ Fi.CI.IGT: success for Introduce drm scaling filter property (rev8) 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=160253607220.31908.1335597437219994573@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=pankaj.laxminarayan.bharadiya@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.