From: Jeremy Fitzhardinge <jeremy@goop.org>
To: M A Young <m.a.young@durham.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: Mangled commit in xen/next-2.6.38
Date: Wed, 09 Feb 2011 14:21:41 -0800 [thread overview]
Message-ID: <4D531375.1030507@goop.org> (raw)
In-Reply-To: <alpine.LFD.2.02.1102092109530.32245@vega3.dur.ac.uk>
On 02/09/2011 01:11 PM, M A Young wrote:
> On Wed, 9 Feb 2011, M A Young wrote:
>
>> Building current xen/next-2.6.38 fails, and it looks like commit
>> 11b0c549fc7a0b0cc6c14f50692696c5bcfb4754 is slightly mangled because
>> it puts the call to trace_xen_mmu_flush_tlb_single in the
>> xen_flush_tlb function and to trace_xen_mmu_flush_tlb in
>> xen_flush_tlb_single
Thanks. That was only half-merged, and I've been meaning to test it
properly.
J
>
> And there are further errors breaking the compile such as
> include/trace/events/xen.h: In function
> 'ftrace_raw_output_xen_mmu_set_pud':
> include/trace/events/xen.h:239:1: error: implicit declaration of
> function 'native_make_pud' [-Werror=implicit-function-declaration]
> include/trace/events/xen.h:239:1: error: request for member 'pgd' in
> something not a structure or union
> In file included from include/trace/ftrace.h:554:0,
> from include/trace/define_trace.h:96,
> from include/trace/events/xen.h:515,
> from arch/x86/xen/trace.c:63:
> include/trace/events/xen.h: In function
> 'ftrace_raw_event_xen_mmu_set_pud':
> include/trace/events/xen.h:239:1: error: 'pud_t' has no member named
> 'pud'
> In file included from include/trace/ftrace.h:758:0,
> from include/trace/define_trace.h:96,
> from include/trace/events/xen.h:515,
> from arch/x86/xen/trace.c:63:
> include/trace/events/xen.h: In function 'perf_trace_xen_mmu_set_pud':
> include/trace/events/xen.h:239:1: error: 'pud_t' has no member named
> 'pud'
>
> Michael Young
>
next prev parent reply other threads:[~2011-02-09 22:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 20:42 Mangled commit in xen/next-2.6.38 M A Young
2011-02-09 21:11 ` M A Young
2011-02-09 22:21 ` Jeremy Fitzhardinge [this message]
2011-02-11 22:20 ` M A Young
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=4D531375.1030507@goop.org \
--to=jeremy@goop.org \
--cc=m.a.young@durham.ac.uk \
--cc=xen-devel@lists.xensource.com \
/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.