From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Wambui Karuga" <wambui.karugax@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/perf: conversion to struct drm_device based logging macros.
Date: Wed, 19 Feb 2020 00:59:02 -0000 [thread overview]
Message-ID: <158207394259.21062.2140394633346421555@emeril.freedesktop.org> (raw)
In-Reply-To: <20200218173936.19664-1-wambui.karugax@gmail.com>
== Series Details ==
Series: drm/i915/perf: conversion to struct drm_device based logging macros.
URL : https://patchwork.freedesktop.org/series/73589/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
2da597adb589 drm/i915/perf: conversion to struct drm_device based logging macros.
-:17: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#17:
References: https://lists.freedesktop.org/archives/dri-devel/2020-January/253381.html
total: 0 errors, 1 warnings, 0 checks, 69 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:[~2020-02-19 0:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 17:39 [Intel-gfx] [PATCH v2] drm/i915/perf: conversion to struct drm_device based logging macros Wambui Karuga
2020-02-19 0:59 ` Patchwork [this message]
2020-02-19 1:22 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2020-02-19 10:30 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/perf: conversion to struct drm_device based logging macros. (rev2) Patchwork
2020-02-19 11:04 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-02-20 23:41 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-02-21 9:36 ` [Intel-gfx] [PATCH v2] drm/i915/perf: conversion to struct drm_device based logging macros Jani Nikula
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=158207394259.21062.2140394633346421555@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=wambui.karugax@gmail.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.