From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 206799] New: Strange help text for KVM_WERROR ("i915")
Date: Mon, 09 Mar 2020 14:49:17 +0000 [thread overview]
Message-ID: <bug-206799-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=206799
Bug ID: 206799
Summary: Strange help text for KVM_WERROR ("i915")
Product: Virtualization
Version: unspecified
Kernel Version: 5.6-rc5
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: low
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: bugzilla.kernel.bpeb@manchmal.in-ulm.de
Regression: No
Commit 4f337faf ("KVM: allow disabling -Werror") introduced the KVM_WERROR
configuration variable, and a help text in Kconfig "Add -Werror to the build
flags for (and only for) i915.ko.". Now I fail to see how this is related to
the i915 video driver, and there is no other mentioning of "915" in that
subtree either - care to check?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2020-03-09 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 14:49 bugzilla-daemon [this message]
2020-03-09 15:24 ` [Bug 206799] Strange help text for KVM_WERROR ("i915") 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-206799-28872@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox