linux-kernel - [PATCH 2/2] xen: remove bm_rld_set of xen_processor

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1370333128-11412-2-git-send-email-lig.fnst@cn.fujitsu.com>
Date:	Tue, 4 Jun 2013 16:05:28 +0800
From:	liguang <lig.fnst@...fujitsu.com>
To:	Len Brown <lenb@...nel.org>, "Rafael J. Wysocki" <rjw@...k.pl>,
	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
	Stefano Stabellini <stefano.stabellini@...citrix.com>
Cc:	Jeremy Fitzhardinge <jeremy@...p.org>,
	Liu Jinsong <jinsong.liu@...el.com>,
	Jan Beulich <JBeulich@...e.com>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
	xen-devel@...ts.xensource.com,
	virtualization@...ts.linux-foundation.org,
	liguang <lig.fnst@...fujitsu.com>
Subject: [PATCH 2/2] xen: remove bm_rld_set of xen_processor_flags

bm_rld_set seems obsolete now

Signed-off-by: liguang <lig.fnst@...fujitsu.com>
---
 include/xen/interface/platform.h |    1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/include/xen/interface/platform.h b/include/xen/interface/platform.h
index c57d5f6..7ffff33 100644
--- a/include/xen/interface/platform.h
+++ b/include/xen/interface/platform.h
@@ -240,7 +240,6 @@ struct xen_processor_flags {
 	uint32_t bm_check:1;
 	uint32_t has_cst:1;
 	uint32_t power_setup_done:1;
-	uint32_t bm_rld_set:1;
 };
 
 struct xen_processor_power {
-- 
1.7.2.5

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/