From: Peter Zijlstra <peterz@infradead.org>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] ✗ Fi.CI.BUILD: failure for mm: Unexport apply_to_page_range()
Date: Mon, 12 Apr 2021 11:23:12 +0200 [thread overview]
Message-ID: <YHQRgLvrvxv/zvtG@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <161821801624.8701.512016472387524468@emeril.freedesktop.org>
On Mon, Apr 12, 2021 at 09:00:16AM -0000, Patchwork wrote:
> == Series Details ==
>
> Series: mm: Unexport apply_to_page_range()
> URL : https://patchwork.freedesktop.org/series/88943/
> State : failure
>
> == Summary ==
>
> CALL scripts/checksyscalls.sh
> CALL scripts/atomic/check-atomics.sh
> DESCEND objtool
> CHK include/generated/compile.h
> Kernel: arch/x86/boot/bzImage is ready (#1)
> MODPOST Module.symvers
> ERROR: modpost: "apply_to_page_range" [drivers/gpu/drm/i915/i915.ko] undefined!
This would be your robot not including the remap_pfn_range_notrack()
patches from Christoph I suppose..
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2021-04-12 9:23 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 8:00 [Intel-gfx] [PATCH 0/7] mm: Unexport apply_to_page_range() Peter Zijlstra
2021-04-12 8:00 ` [Intel-gfx] [PATCH 1/7] mm: Unexport apply_to_existing_page_range() Peter Zijlstra
2021-04-12 8:13 ` Christoph Hellwig
2021-04-12 8:00 ` [Intel-gfx] [PATCH 2/7] xen/gntdev, x86: Remove apply_to_page_range() use from module Peter Zijlstra
2021-04-12 8:26 ` Christoph Hellwig
2021-04-12 9:20 ` Peter Zijlstra
2021-04-12 9:26 ` Juergen Gross
2021-04-12 8:00 ` [Intel-gfx] [PATCH 3/7] xen/gntdev: " Peter Zijlstra
2021-04-12 8:27 ` Christoph Hellwig
2021-04-12 9:02 ` Peter Zijlstra
2021-04-12 8:00 ` [Intel-gfx] [PATCH 4/7] mm: Introduce verify_page_range() Peter Zijlstra
2021-04-12 8:28 ` Christoph Hellwig
2021-04-12 9:17 ` Peter Zijlstra
2021-04-12 20:05 ` Kees Cook
2021-04-13 6:54 ` Peter Zijlstra
2021-04-19 23:36 ` Kees Cook
2021-04-13 7:36 ` Peter Zijlstra
2021-04-14 3:01 ` Kees Cook
2021-04-14 7:00 ` Peter Zijlstra
2021-04-12 8:00 ` [Intel-gfx] [PATCH 5/7] xen/privcmd: Use verify_page_range() Peter Zijlstra
2021-04-12 8:28 ` Christoph Hellwig
2021-04-12 8:00 ` [Intel-gfx] [PATCH 6/7] i915: Convert to verify_page_range() Peter Zijlstra
2021-04-12 8:28 ` Christoph Hellwig
2021-04-12 20:08 ` Kees Cook
2021-04-13 6:54 ` Peter Zijlstra
2021-04-14 3:04 ` Kees Cook
2021-04-12 8:00 ` [Intel-gfx] [PATCH 7/7] mm: Unexport apply_to_page_range() Peter Zijlstra
2021-04-12 8:28 ` Christoph Hellwig
2021-04-12 9:00 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for " Patchwork
2021-04-12 9:23 ` Peter Zijlstra [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=YHQRgLvrvxv/zvtG@hirez.programming.kicks-ass.net \
--to=peterz@infradead.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