From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: rjw@rjwysocki.net
Cc: rdunlap@infradead.org, viresh.kumar@linaro.org,
"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
"Srivatsa S. Bhat" <srivatsa@mit.edu>,
linux-pm@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] PM / Documentation: Update Srivatsa S. Bhat's email address
Date: Mon, 09 Jun 2014 15:54:49 +0530 [thread overview]
Message-ID: <20140609102426.26530.15670.stgit@srivatsabhat.in.ibm.com> (raw)
My @linux.vnet.ibm.com email address is going to disappear soon, as I will be
beginning my M.S./PhD studies at MIT in a few months. So update my email
address in the documentation.
Signed-off-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
Signed-off-by: Srivatsa S. Bhat <srivatsa@mit.edu>
---
Documentation/power/suspend-and-cpuhotplug.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/power/suspend-and-cpuhotplug.txt b/Documentation/power/suspend-and-cpuhotplug.txt
index e13dafc..3813703 100644
--- a/Documentation/power/suspend-and-cpuhotplug.txt
+++ b/Documentation/power/suspend-and-cpuhotplug.txt
@@ -1,6 +1,6 @@
Interaction of Suspend code (S3) with the CPU hotplug infrastructure
- (C) 2011 Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
+ (C) 2011-2014 Srivatsa S. Bhat <srivatsa@mit.edu>
I. How does the regular CPU hotplug code differ from how the Suspend-to-RAM
next reply other threads:[~2014-06-09 10:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 10:24 Srivatsa S. Bhat [this message]
2014-06-09 10:32 ` Viresh Kumar
2014-06-09 10:42 ` Srivatsa S. Bhat
2014-06-09 11:28 ` Rafael J. Wysocki
2014-06-09 11:23 ` Srivatsa S. Bhat
2014-06-09 12:17 ` Srivatsa S. Bhat
2014-06-14 22:36 ` company copyrights. " Pavel Machek
2014-06-15 22:56 ` Rafael J. Wysocki
2014-06-16 6:58 ` Pavel Machek
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=20140609102426.26530.15670.stgit@srivatsabhat.in.ibm.com \
--to=srivatsa.bhat@linux.vnet.ibm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=srivatsa@mit.edu \
--cc=viresh.kumar@linaro.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
all inboxes | Powered by JetHome®