From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Ro.CI.BAT: failure for mm/slub: Run free_partial() outside of the kmem_cache_node->list_lock
Date: Wed, 10 Aug 2016 08:03:29 -0000 [thread overview]
Message-ID: <20160810080329.24580.11130@emeril.freedesktop.org> (raw)
In-Reply-To: <1470756533-13591-1-git-send-email-chris@chris-wilson.co.uk>
== Series Details ==
Series: mm/slub: Run free_partial() outside of the kmem_cache_node->list_lock
URL : https://patchwork.freedesktop.org/series/10854/
State : failure
== Summary ==
Applying: mm/slub: Run free_partial() outside of the kmem_cache_node->list_lock
Using index info to reconstruct a base tree...
M mm/slub.c
Falling back to patching base and 3-way merge...
Auto-merging mm/slub.c
CONFLICT (content): Merge conflict in mm/slub.c
error: Failed to merge in the changes.
Patch failed at 0001 mm/slub: Run free_partial() outside of the kmem_cache_node->list_lock
The copy of the patch that failed is found in: .git/rebase-apply/patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-08-10 8:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 15:28 [CI] mm/slub: Run free_partial() outside of the kmem_cache_node->list_lock Chris Wilson
2016-08-10 8:03 ` Patchwork [this message]
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=20160810080329.24580.11130@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox