From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Bob Paauwe" <bob.j.paauwe@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Adding YUV444 packed format support for skl+ (rev5)
Date: Tue, 07 Apr 2020 22:52:07 -0000 [thread overview]
Message-ID: <158629992733.26325.4905844482068045895@emeril.freedesktop.org> (raw)
In-Reply-To: <20200407215546.5445-1-bob.j.paauwe@intel.com>
== Series Details ==
Series: Adding YUV444 packed format support for skl+ (rev5)
URL : https://patchwork.freedesktop.org/series/73020/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
6c533ea6ac21 drm/i915: Adding YUV444 packed format support for skl+ (V15)
-:9: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#9:
PLANE_CTL_FORMAT_AYUV is already supported, according to hardware specification.
total: 0 errors, 1 warnings, 0 checks, 87 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-04-07 22:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 21:55 [Intel-gfx] [PATCH 0/1] Adding YUV444 packed format support for skl+ Bob Paauwe
2020-04-07 21:55 ` [Intel-gfx] [PATCH 1/1] drm/i915: Adding YUV444 packed format support for skl+ (V15) Bob Paauwe
2020-04-08 7:45 ` Jani Nikula
2020-04-16 9:10 ` Jani Nikula
2020-04-16 22:45 ` Paauwe, Bob J
2020-04-17 6:31 ` Jani Nikula
2020-04-07 22:52 ` Patchwork [this message]
2020-04-07 23:19 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for Adding YUV444 packed format support for skl+ (rev5) Patchwork
2020-04-07 23:48 ` Paauwe, Bob J
2020-04-08 7:43 ` Saarinen, Jani
2020-04-08 13:12 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-04-08 22:39 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=158629992733.26325.4905844482068045895@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=bob.j.paauwe@intel.com \
--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.