From: Avi Kivity <avi@redhat.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
akpm <akpm@linux-foundation.org>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
kvm@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH -next] kvm: fix TASK_DELAY_ACCT kconfig warning
Date: Wed, 27 Jul 2011 14:19:31 +0300 [thread overview]
Message-ID: <4E2FF443.3070104@redhat.com> (raw)
In-Reply-To: <20110725110109.b06fe691.rdunlap@xenotime.net>
On 07/25/2011 09:01 PM, Randy Dunlap wrote:
> From: Randy Dunlap<rdunlap@xenotime.net>
>
> Fix kconfig dependency warning:
>
> warning: (KVM) selects TASK_DELAY_ACCT which has unmet direct dependencies (TASKSTATS)
Applied, thanks.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-07-27 11:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-25 6:25 linux-next: Tree for July 25 Stephen Rothwell
2011-07-25 16:19 ` [PATCH -next] watchdog: fix it8712f_wdt build errors Randy Dunlap
2011-07-25 19:02 ` Wim Van Sebroeck
2011-07-25 18:01 ` [PATCH -next] kvm: fix TASK_DELAY_ACCT kconfig warning Randy Dunlap
2011-07-27 11:19 ` Avi Kivity [this message]
2011-07-25 21:46 ` linux-next: Tree for July 25 (xen) Randy Dunlap
2011-08-04 19:35 ` Ingo Molnar
2011-08-04 19:55 ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-08-04 20:15 ` Randy Dunlap
2011-08-04 22:30 ` [Xen-devel] " Konrad Rzeszutek Wilk
2011-08-04 23:22 ` Randy Dunlap
2011-08-04 22:32 ` Konrad Rzeszutek Wilk
2011-08-04 22:40 ` Konrad Rzeszutek Wilk
2011-08-04 23:24 ` Randy Dunlap
2011-08-04 23:53 ` Randy Dunlap
2011-08-05 8:05 ` Ingo Molnar
2011-08-05 21:14 ` Ingo Molnar
2011-08-06 1:58 ` Konrad Rzeszutek Wilk
2011-08-06 7:04 ` Stephen Rothwell
2011-08-06 18:22 ` Jeremy Fitzhardinge
2011-08-08 13:01 ` Steven Rostedt
2011-08-10 16:49 ` Jeremy Fitzhardinge
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=4E2FF443.3070104@redhat.com \
--to=avi@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).