All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 115081] arch/x86/kvm/vmx.c:8719: Error: symbol `vmx_return' is already defined
Date: Thu, 31 Mar 2016 03:12:41 +0000	[thread overview]
Message-ID: <bug-115081-28872-ZIsqQoDsTQ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-115081-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=115081

--- Comment #21 from Linda Walsh <lkml@tlinx.org> ---
That allows it to compile -- though it may be a while before I can test it
live.

The time between boots on my system tends toward large, due to difficulties I
usually have in the suse boot process not being very reliable due to being
in constant, backward-incompatible change, (last uptime was over 100 days,
while currently am at 33 days w/4.4.3).

That said, though, since there seem to be no overt code changes and mostly
directives to the compiler to stop misbehaving, I suspect it should work fine.

Thing I don't understand is why it compiled in 4.4.3 but not 4.5...knowing that
would at least easy my curiosity if not my mind...  ;-)

BTW -- sent the 2nd copy as my mailer farted halfway through sending, and I
wasn't sure it went out (no record of it having gone out in mail-record file or
in the mail.info log file, thus the 2nd copy).

Thanks for the quick turnaround...

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2016-03-31  3:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-21 23:16 [Bug 115081] New: arch/x86/kvm/vmx.c:8719: Error: symbol `vmx_return' is already defined bugzilla-daemon
2016-03-21 23:17 ` [Bug 115081] " bugzilla-daemon
2016-03-23 20:09 ` bugzilla-daemon
2016-03-24  2:46 ` bugzilla-daemon
2016-03-24  3:54 ` bugzilla-daemon
2016-03-24  4:19 ` bugzilla-daemon
2016-03-24  8:30 ` bugzilla-daemon
2016-03-24 13:31 ` bugzilla-daemon
2016-03-24 13:34 ` bugzilla-daemon
2016-03-25 17:11 ` bugzilla-daemon
2016-03-25 17:19 ` bugzilla-daemon
2016-03-29  9:48 ` bugzilla-daemon
2016-03-29 16:44 ` bugzilla-daemon
2016-03-29 16:45 ` bugzilla-daemon
2016-03-29 16:45 ` bugzilla-daemon
2016-03-29 16:54 ` bugzilla-daemon
2016-03-29 16:54 ` bugzilla-daemon
2016-03-29 16:55 ` bugzilla-daemon
2016-03-29 16:57 ` bugzilla-daemon
2016-03-29 17:18 ` bugzilla-daemon
2016-03-29 17:27 ` bugzilla-daemon
2016-03-29 17:55 ` bugzilla-daemon
2016-03-30  9:18 ` bugzilla-daemon
2016-03-31  3:12 ` bugzilla-daemon [this message]
2016-03-31  3:13 ` bugzilla-daemon

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=bug-115081-28872-ZIsqQoDsTQ@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@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 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.