From: "Matthew R. Ochs" <mrochs@linux.vnet.ibm.com>
To: Frederic Barrat <fbarrat@linux.vnet.ibm.com>
Cc: imunsie@au1.ibm.com, michael.neuling@au1.ibm.com,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] cxl: Fix PSL timebase synchronization detection
Date: Wed, 24 Feb 2016 12:13:58 -0600 [thread overview]
Message-ID: <801CF454-A605-446A-92E6-A947996E2C3D@linux.vnet.ibm.com> (raw)
In-Reply-To: <1456334871-30397-1-git-send-email-fbarrat@linux.vnet.ibm.com>
Reviewed-by: Matthew R. Ochs <mrochs@linux.vnet.ibm.com>
next prev parent reply other threads:[~2016-02-24 18:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 17:27 [PATCH] cxl: Fix PSL timebase synchronization detection Frederic Barrat
2016-02-24 17:37 ` Michael Neuling
2016-02-24 18:13 ` Matthew R. Ochs [this message]
2016-02-25 0:20 ` Ian Munsie
2016-02-25 0:30 ` Andrew Donnellan
2016-02-25 1:19 ` Vaibhav Jain
2016-02-29 11:01 ` Michael Ellerman
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=801CF454-A605-446A-92E6-A947996E2C3D@linux.vnet.ibm.com \
--to=mrochs@linux.vnet.ibm.com \
--cc=fbarrat@linux.vnet.ibm.com \
--cc=imunsie@au1.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michael.neuling@au1.ibm.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;
as well as URLs for NNTP newsgroup(s).