From: Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>
To: <bp@suse.de>, <gregkh@linuxfoundation.org>
Cc: <sudeep.holla@arm.com>, <sboyd@codeaurora.org>,
<linux-api@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH] Docmentation, ABI: Update contact for L3 cache index disable
Date: Fri, 8 May 2015 17:44:58 -0500 [thread overview]
Message-ID: <1431125098-9470-1-git-send-email-Aravind.Gopalakrishnan@amd.com> (raw)
The mailing list discuss@x86-64.org is now defunct.
Using x86@kernel.org in its place.
Signed-off-by: Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>
---
Documentation/ABI/testing/sysfs-devices-system-cpu | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/ABI/testing/sysfs-devices-system-cpu b/Documentation/ABI/testing/sysfs-devices-system-cpu
index 99983e6..f1c46d0 100644
--- a/Documentation/ABI/testing/sysfs-devices-system-cpu
+++ b/Documentation/ABI/testing/sysfs-devices-system-cpu
@@ -162,7 +162,7 @@ Description: Discover CPUs in the same CPU frequency coordination domain
What: /sys/devices/system/cpu/cpu*/cache/index3/cache_disable_{0,1}
Date: August 2008
KernelVersion: 2.6.27
-Contact: discuss@x86-64.org
+Contact: x86@kernel.org
Description: Disable L3 cache indices
These files exist in every CPU's cache/index3 directory. Each
--
2.4.0
next reply other threads:[~2015-05-08 22:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 22:44 Aravind Gopalakrishnan [this message]
2015-05-14 9:25 ` Borislav Petkov
2015-05-18 8:07 [PATCH 0/2] tip queue 2015-05-18 Borislav Petkov
2015-05-18 8:07 ` [PATCH 1/2] Documentation/ABI: Update contact for L3 cache index disable Borislav Petkov
2015-05-18 9:11 ` [tip:x86/urgent] x86/Documentation: Update the contact email for L3 cache index disable functionality tip-bot for Aravind Gopalakrishnan
2015-05-18 8:07 ` [PATCH 2/2] x86/mce: Use only critical MCE severity message Borislav Petkov
2015-05-18 9:11 ` [tip:x86/urgent] x86/mce: Fix MCE severity messages tip-bot for Borislav Petkov
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=1431125098-9470-1-git-send-email-Aravind.Gopalakrishnan@amd.com \
--to=aravind.gopalakrishnan@amd.com \
--cc=bp@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyd@codeaurora.org \
--cc=sudeep.holla@arm.com \
/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
all inboxes | Powered by JetHome®