From: Alex Williamson <alex.williamson@redhat•com>
To: Randy Dunlap <rdunlap@xenotime•net>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
KVM <kvm@vger•kernel.org>
Subject: Re: linux-next: Tree for Jun 27 (vfio)
Date: Wed, 27 Jun 2012 13:20:37 -0600 [thread overview]
Message-ID: <1340824837.1207.221.camel@bling.home> (raw)
In-Reply-To: <4FEB3030.9070900@xenotime.net>
On Wed, 2012-06-27 at 09:09 -0700, Randy Dunlap wrote:
> On 06/26/2012 08:22 PM, Stephen Rothwell wrote:
>
> > Hi all,
> >
> > This tree was not built between each merge, but only after merging all
> > the trees.
> >
> > Changes since 20120626:
> >
> > New tree: vfio
>
>
> on x86_64:
>
> CC [M] drivers/vfio/vfio.o
> drivers/vfio/vfio.c: In function 'vfio_device_release':
> drivers/vfio/vfio.c:412:2: error: 'TASK_NORMAL' undeclared (first use in this function)
> drivers/vfio/vfio.c:412:2: note: each undeclared identifier is reported only once for each function it appears in
> drivers/vfio/vfio.c: In function 'vfio_del_group_dev':
>
> drivers/vfio/vfio.c:695:2: error: 'TASK_UNINTERRUPTIBLE' undeclared (first use in this function)
> drivers/vfio/vfio.c:695:2: error: implicit declaration of function 'schedule'
> *** [drivers/vfio/vfio.o] Error 1
>
>
> Full randconfig file is attached.
Thanks for the report, this should be fixed in tomorrow's tree. Thanks,
Alex
next prev parent reply other threads:[~2012-06-27 19:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 3:22 linux-next: Tree for Jun 27 Stephen Rothwell
2012-06-27 16:09 ` linux-next: Tree for Jun 27 (vfio) Randy Dunlap
2012-06-27 19:20 ` Alex Williamson [this message]
2012-06-27 16:13 ` linux-next: Tree for Jun 27 (dm-thin.c) Randy Dunlap
2012-06-27 16:18 ` Alasdair G Kergon
2012-06-27 16:25 ` linux-next: Tree for Jun 27 (eliminated_printk) Randy Dunlap
2012-06-27 16:29 ` Joe Perches
2012-06-27 22:52 ` Stephen Rothwell
2012-06-28 20:14 ` Shuah Khan
2012-06-28 20:16 ` Matthew Garrett
2012-06-28 21:03 ` Shuah Khan
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=1340824837.1207.221.camel@bling.home \
--to=alex.williamson@redhat$(echo .)com \
--cc=kvm@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rdunlap@xenotime$(echo .)net \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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