From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Arnd Bergmann" <arnd@arndb.de>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for i915: fix backlight configuration issue
Date: Wed, 08 Jan 2020 14:36:10 -0000 [thread overview]
Message-ID: <157849417035.23226.17825722690598324847@emeril.freedesktop.org> (raw)
In-Reply-To: <20200108140227.3976563-1-arnd@arndb.de>
== Series Details ==
Series: i915: fix backlight configuration issue
URL : https://patchwork.freedesktop.org/series/71766/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
3237c6dfef7c i915: fix backlight configuration issue
-:12: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#12:
intel_panel.c:(.text+0x2f58): undefined reference to `backlight_device_register'
-:41: WARNING:CONFIG_DESCRIPTION: please write a paragraph that describes the config symbol fully
#41: FILE: drivers/gpu/drm/i915/Kconfig:71:
+config DRM_I915_BACKLIGHT
total: 0 errors, 2 warnings, 0 checks, 58 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-01-08 14:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 14:01 [PATCH] i915: fix backlight configuration issue Arnd Bergmann
2020-01-08 14:01 ` [Intel-gfx] " Arnd Bergmann
2020-01-08 14:01 ` Arnd Bergmann
2020-01-08 14:36 ` Patchwork [this message]
2020-01-08 15:05 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-01-08 15:32 ` [PATCH] " Jani Nikula
2020-01-08 15:32 ` [Intel-gfx] " Jani Nikula
2020-01-08 15:32 ` Jani Nikula
2020-01-08 18:55 ` Daniel Vetter
2020-01-08 18:55 ` [Intel-gfx] " Daniel Vetter
2020-01-08 18:55 ` Daniel Vetter
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=157849417035.23226.17825722690598324847@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=arnd@arndb.de \
--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 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.