From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Daniel Stodden <daniel.stodden@citrix.com>
Cc: jeremy@goop.org, Xen <xen-devel@lists.xensource.com>,
Ian.Campbell@citrix.com
Subject: Re: trouble building 2.6.38: 'IRQF_FORCE_RESUME' undeclared
Date: Thu, 3 Mar 2011 16:03:04 -0500 [thread overview]
Message-ID: <20110303210304.GA6526@dumpdata.com> (raw)
In-Reply-To: <1299185575-17375-1-git-send-email-daniel.stodden@citrix.com>
On Thu, Mar 03, 2011 at 12:52:54PM -0800, Daniel Stodden wrote:
> Iirc I derived this from a prior commit from either Ian or Jeremy.
>
> Didn't really check it out, so there's very likely a more correct fix
> than what's attached here.
>
> /local/exp/dns/scratch/xenbits/xen-unstable.hg/linux-2.6-pvops.git/arch/x86/xen/time.c: In function 'xen_setup_timer':
> /local/exp/dns/scratch/xenbits/xen-unstable.hg/linux-2.6-pvops.git/arch/x86/xen/time.c:402: error: 'IRQF_FORCE_RESUME' undeclared (first use in this function)
> /local/exp/dns/scratch/xenbits/xen-unstable.hg/linux-2.6-pvops.git/arch/x86/xen/time.c:402: error: (Each undeclared identifier is reported only once
> /local/exp/dns/scratch/xenbits/xen-unstable.hg/linux-2.6-pvops.git/arch/x86/xen/time.c:402: error: for each function it appears in.)
>
Uh, what git tree is that?
> This reproducible?
>
> Thanks,
> Daniel
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2011-03-03 21:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 20:52 trouble building 2.6.38: 'IRQF_FORCE_RESUME' undeclared Daniel Stodden
2011-03-03 20:52 ` [PATCH] kernel: Fix pvops build on 2.6.38 Daniel Stodden
2011-03-04 10:19 ` Ian Campbell
2011-03-03 21:03 ` Konrad Rzeszutek Wilk [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=20110303210304.GA6526@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=daniel.stodden@citrix.com \
--cc=jeremy@goop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).