From: Patchwork <patchwork@emeril.freedesktop.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BAT: failure for series starting with [1/4] mm: Check if mmu notifier callbacks are allowed to fail
Date: Mon, 20 May 2019 21:46:57 -0000 [thread overview]
Message-ID: <20190520214657.784.16337@emeril.freedesktop.org> (raw)
In-Reply-To: <20190520213945.17046-1-daniel.vetter@ffwll.ch>
== Series Details ==
Series: series starting with [1/4] mm: Check if mmu notifier callbacks are allowed to fail
URL : https://patchwork.freedesktop.org/series/60874/
State : failure
== Summary ==
CALL scripts/checksyscalls.sh
CALL scripts/atomic/check-atomics.sh
DESCEND objtool
CHK include/generated/compile.h
CC kernel/sched/core.o
kernel/sched/core.c: In function ‘schedule_debug’:
kernel/sched/core.c:3277:33: error: ‘struct task_struct’ has no member named ‘non_blocking_count’; did you mean ‘non_block_count’?
prev->comm, prev->pid, prev->non_blocking_count);
^~~~~~~~~~~~~~~~~~
non_block_count
scripts/Makefile.build:278: recipe for target 'kernel/sched/core.o' failed
make[2]: *** [kernel/sched/core.o] Error 1
scripts/Makefile.build:489: recipe for target 'kernel/sched' failed
make[1]: *** [kernel/sched] Error 2
Makefile:1071: recipe for target 'kernel' failed
make: *** [kernel] Error 2
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-05-20 21:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 21:39 [PATCH 1/4] mm: Check if mmu notifier callbacks are allowed to fail Daniel Vetter
2019-05-20 21:39 ` [PATCH 2/4] kernel.h: Add non_block_start/end() Daniel Vetter
2019-05-20 21:39 ` Daniel Vetter
2019-05-21 14:47 ` [PATCH] " Daniel Vetter
2019-05-21 14:47 ` Daniel Vetter
2019-05-20 21:39 ` [PATCH 3/4] mm, notifier: Catch sleeping/blocking for !blockable Daniel Vetter
2019-05-21 15:32 ` Jerome Glisse
2019-05-20 21:39 ` [PATCH 4/4] mm, notifier: Add a lockdep map for invalidate_range_start Daniel Vetter
2019-05-21 15:40 ` Jerome Glisse
2019-05-21 16:00 ` Daniel Vetter
2019-05-21 16:32 ` Jerome Glisse
2019-05-20 21:46 ` Patchwork [this message]
2019-05-21 15:44 ` [PATCH 1/4] mm: Check if mmu notifier callbacks are allowed to fail Jerome Glisse
2019-06-18 15:22 ` Daniel Vetter
2019-06-18 15:22 ` Daniel Vetter
2019-06-19 16:50 ` Jason Gunthorpe
2019-06-19 19:57 ` Daniel Vetter
2019-06-19 20:13 ` Jason Gunthorpe
2019-06-19 20:18 ` Daniel Vetter
2019-06-19 20:42 ` Jason Gunthorpe
2019-06-19 21:20 ` Daniel Vetter
2019-05-21 17:54 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/4] mm: Check if mmu notifier callbacks are allowed to fail (rev2) Patchwork
2019-05-21 18:14 ` ✓ Fi.CI.BAT: success " Patchwork
2019-05-22 12:21 ` ✗ 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=20190520214657.784.16337@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=daniel.vetter@ffwll.ch \
--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.