From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Chris Wilson" <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for HAX sched/core: Paper over the ttwu() race
Date: Mon, 20 Jul 2020 17:41:40 -0000 [thread overview]
Message-ID: <159526690056.13114.6328625312616335552@emeril.freedesktop.org> (raw)
In-Reply-To: <20200720173016.29756-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: HAX sched/core: Paper over the ttwu() race
URL : https://patchwork.freedesktop.org/series/79682/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
61aff133b9cc HAX sched/core: Paper over the ttwu() race
-:8: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#8:
<4> [181.766629] WARNING: CPU: 0 PID: 1524 at kernel/sched/core.c:2388 ttwu_queue_wakelist+0xbc/0xd0
-:43: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit b6e13e85829f ("sched/core: Fix ttwu() race")'
#43:
References: b6e13e85829f ("sched/core: Fix ttwu() race")
total: 1 errors, 1 warnings, 0 checks, 9 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-07-20 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 17:30 [Intel-gfx] [CI] HAX sched/core: Paper over the ttwu() race Chris Wilson
2020-07-20 17:41 ` Patchwork [this message]
2020-07-20 18:03 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-07-20 19:28 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=159526690056.13114.6328625312616335552@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--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.