From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
jeremy@xensource.com, chrisw@sous-sol.org,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
virtualization@lists.osdl.org
Subject: Re: linux-next: Tree for June 18 (XEN build error)
Date: Thu, 19 Jun 2008 15:54:51 +1000 [thread overview]
Message-ID: <20080619155451.0a4ea6f8.sfr@canb.auug.org.au> (raw)
In-Reply-To: <4859E9B8.9040406@goop.org>
[-- Attachment #1: Type: text/plain, Size: 882 bytes --]
On Wed, 18 Jun 2008 22:08:08 -0700 Jeremy Fitzhardinge <jeremy@goop.org> wrote:
>
> Randy Dunlap wrote:
> > linux-next-20080618/drivers/xen/manage.c: In function 'xen_suspend':
> > linux-next-20080618/drivers/xen/manage.c:66: error: too few arguments to function 'device_power_up'
> > linux-next-20080618/drivers/xen/manage.c: In function 'do_suspend':
> > linux-next-20080618/drivers/xen/manage.c:115: error: too few arguments to function 'device_resume'
> > make[3]: *** [drivers/xen/manage.o] Error 1
> >
>
> What argument(s) do device_power_up() and device_resume() want now?
In today's linux-next:
void device_power_up(pm_message_t state)
void device_resume(pm_message_t state)
If someone can give me a patch, I can carry it in linux-next ...
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2008-06-19 5:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 7:57 linux-next: Tree for June 18 Stephen Rothwell
2008-06-18 19:43 ` linux-next: Tree for June 18 (XEN build error) Randy Dunlap
2008-06-19 5:08 ` Jeremy Fitzhardinge
2008-06-19 5:54 ` Stephen Rothwell [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=20080619155451.0a4ea6f8.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=chrisw@sous-sol.org \
--cc=jeremy@goop.org \
--cc=jeremy@xensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=virtualization@lists.osdl.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.