From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Avi Kivity <avi@qumranet.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Gleb Natapov <gleb@redhat.com>
Subject: linux-next: kvm tree build warning
Date: Mon, 6 Jul 2009 11:37:52 +1000 [thread overview]
Message-ID: <20090706113752.8dec663a.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 440 bytes --]
Hi Avi,
Today's linux-next build (x86_64_allmodconfig) produced this warning:
arch/x86/kvm/lapic.c: In function 'apic_mmio_write':
arch/x86/kvm/lapic.c:834: warning: 'return' with no value, in function returning non-void
Introduced by commit 55b23c7377c9f9f0b4a4b90950f0e18b26ac45e8 ("KVM:
x2apic interface to lapic").
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-07-06 1:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 1:37 Stephen Rothwell [this message]
2009-07-06 5:28 ` linux-next: kvm tree build warning Gleb Natapov
2009-07-06 6:01 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2010-01-11 8:25 Stephen Rothwell
2010-01-20 6:38 Stephen Rothwell
2010-01-20 6:48 Stephen Rothwell
2010-01-20 10:42 ` Alexander Graf
2010-01-20 13:01 ` Stephen Rothwell
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=20090706113752.8dec663a.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=avi@qumranet.com \
--cc=gleb@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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