From: Patchwork <patchwork@emeril.freedesktop.org>
To: Matthew Auld <matthew.auld@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for drm/i915/lmem: add the fake lmem region
Date: Wed, 30 Oct 2019 01:43:57 -0000 [thread overview]
Message-ID: <20191030014357.8997.15349@emeril.freedesktop.org> (raw)
In-Reply-To: <20191029165134.28567-1-matthew.auld@intel.com>
== Series Details ==
Series: drm/i915/lmem: add the fake lmem region
URL : https://patchwork.freedesktop.org/series/68733/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
9fd60b3f26c7 drm/i915/lmem: add the fake lmem region
-:93: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#93: FILE: drivers/gpu/drm/i915/i915_params.c:184:
+i915_param_named_unsafe(fake_lmem_start, ulong, 0600,
+ "Fake LMEM start offset (default: 0)");
total: 0 errors, 0 warnings, 1 checks, 214 lines checked
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Matthew Auld" <matthew.auld@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/lmem: add the fake lmem region
Date: Wed, 30 Oct 2019 01:43:57 -0000 [thread overview]
Message-ID: <20191030014357.8997.15349@emeril.freedesktop.org> (raw)
Message-ID: <20191030014357.v68CfvAhFiBqQEFE98ZZuAwrEHPhFQsCP2Lq7gPeyWo@z> (raw)
In-Reply-To: <20191029165134.28567-1-matthew.auld@intel.com>
== Series Details ==
Series: drm/i915/lmem: add the fake lmem region
URL : https://patchwork.freedesktop.org/series/68733/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
9fd60b3f26c7 drm/i915/lmem: add the fake lmem region
-:93: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#93: FILE: drivers/gpu/drm/i915/i915_params.c:184:
+i915_param_named_unsafe(fake_lmem_start, ulong, 0600,
+ "Fake LMEM start offset (default: 0)");
total: 0 errors, 0 warnings, 1 checks, 214 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:[~2019-10-30 1:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 16:51 [PATCH] drm/i915/lmem: add the fake lmem region Matthew Auld
2019-10-29 16:51 ` [Intel-gfx] " Matthew Auld
2019-10-30 1:43 ` Patchwork [this message]
2019-10-30 1:43 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-10-30 1:57 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-10-30 1:57 ` [Intel-gfx] " Patchwork
2019-10-30 9:14 ` [PATCH] " Chris Wilson
2019-10-30 9:14 ` [Intel-gfx] " Chris Wilson
2019-10-30 22:22 ` Matthew Auld
2019-10-30 22:22 ` [Intel-gfx] " Matthew Auld
2019-10-31 12:40 ` Arkadiusz Hiler
2019-10-31 12:40 ` [Intel-gfx] " Arkadiusz Hiler
2019-10-31 20:40 ` Chris Wilson
2019-10-31 20:40 ` [Intel-gfx] " Chris Wilson
2019-11-05 13:05 ` Matthew Auld
2019-11-05 13:05 ` [Intel-gfx] " Matthew Auld
2019-11-06 8:30 ` Arkadiusz Hiler
2019-11-06 8:30 ` [Intel-gfx] " Arkadiusz Hiler
2019-11-06 11:17 ` Chris Wilson
2019-11-06 11:17 ` [Intel-gfx] " Chris Wilson
2019-11-06 13:58 ` Arkadiusz Hiler
2019-11-06 13:58 ` [Intel-gfx] " Arkadiusz Hiler
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=20191030014357.8997.15349@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@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.