intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Daniel Vetter" <daniel.vetter@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm: Fix oops in damage self-tests by mocking damage property
Date: Fri, 30 Jul 2021 12:32:10 -0000	[thread overview]
Message-ID: <162764833090.582.6320613014043501374@emeril.freedesktop.org> (raw)
In-Reply-To: <20210730095251.4343-1-daniel.vetter@ffwll.ch>

== Series Details ==

Series: drm: Fix oops in damage self-tests by mocking damage property
URL   : https://patchwork.freedesktop.org/series/93233/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
3efd59452f81 drm: Fix oops in damage self-tests by mocking damage property
-:52: ERROR:INITIALISED_STATIC: do not initialise statics to false
#52: FILE: drivers/gpu/drm/selftests/test-drm_damage_helper.c:22:
+	static bool setup_done = false;

-:83: WARNING:TRAILING_SEMICOLON: macros should not use a trailing semicolon
#83: FILE: drivers/gpu/drm/selftests/test-drm_damage_helper.c:107:
+#define MOCK_VARIABLES() \
+	struct drm_plane_state old_state; \
+	struct drm_plane_state state = { \
+		.crtc = ZERO_SIZE_PTR, \
+		.fb = (struct drm_framebuffer *) &fb, \
+		.visible = true, \
+	}; \
+	mock_setup(&old_state); \
+	mock_setup(&state);

-:87: CHECK:SPACING: No space is necessary after a cast
#87: FILE: drivers/gpu/drm/selftests/test-drm_damage_helper.c:111:
+		.fb = (struct drm_framebuffer *) &fb, \

-:572: WARNING:FROM_SIGN_OFF_MISMATCH: From:/Signed-off-by: email address mismatch: 'From: Daniel Vetter <daniel.vetter@ffwll.ch>' != 'Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>'

total: 1 errors, 2 warnings, 1 checks, 516 lines checked



  reply	other threads:[~2021-07-30 12:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-30  9:52 [Intel-gfx] [PATCH] drm: Fix oops in damage self-tests by mocking damage property Daniel Vetter
2021-07-30 12:32 ` Patchwork [this message]
2021-07-30 12:32 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2021-07-30 13:01 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-07-30 14:19 ` [Intel-gfx] [PATCH] " kernel test robot
2021-07-30 14:19 ` [Intel-gfx] [RFC PATCH] drm: mock_device can be static kernel test robot
2021-07-30 21:43 ` [Intel-gfx] ✓ Fi.CI.IGT: success for drm: Fix oops in damage self-tests by mocking damage property Patchwork
2021-08-02  9:10 ` [Intel-gfx] [PATCH] " Maarten Lankhorst

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=162764833090.582.6320613014043501374@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=daniel.vetter@ffwll.ch \
    --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).