From: Patchwork <patchwork@emeril.freedesktop.org>
To: akpm@linux-foundation.org
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for + diff-sucks.patch added to -mm tree
Date: Fri, 05 Jul 2019 05:23:48 -0000 [thread overview]
Message-ID: <20190705052348.29485.79866@emeril.freedesktop.org> (raw)
In-Reply-To: <20190705050948.TPpsTT9oH%akpm@linux-foundation.org>
== Series Details ==
Series: + diff-sucks.patch added to -mm tree
URL : https://patchwork.freedesktop.org/series/63251/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
cdf723d72139 + diff-sucks.patch added to -mm tree
-:22: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#22:
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
total: 0 errors, 1 warnings, 0 checks, 1 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-07-05 5:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 5:09 + diff-sucks.patch added to -mm tree akpm
2019-07-05 5:23 ` Patchwork [this message]
2019-07-05 6:16 ` ✗ Fi.CI.BAT: failure for " 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=20190705052348.29485.79866@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=akpm@linux-foundation.org \
--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).