From: Michael Neuling <mikey@neuling.org>
To: Ian Munsie <imunsie@au1.ibm.com>
Cc: Frederic Barrat <fbarrat@linux.vnet.ibm.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH next] cxl: Allow PSL timebase to not sync
Date: Thu, 17 Mar 2016 13:45:09 +1100 [thread overview]
Message-ID: <1458182709.23128.5.camel@neuling.org> (raw)
In-Reply-To: <1458177720-sup-8617@x230.ozlabs.ibm.com>
> IMO, we should ditch the module parameter altogether and never treat
> timebase sync failure as fatal, and leave that up to any applications
> actually need it to check.
I agree with this this.
Mikey
next prev parent reply other threads:[~2016-03-17 2:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 18:55 [PATCH] cxl: Allow PSL timebase to not sync Frederic Barrat
2016-03-14 19:29 ` [PATCH next] " Frederic Barrat
2016-03-15 0:27 ` Michael Neuling
2016-03-15 3:56 ` Michael Ellerman
2016-03-16 11:32 ` Frederic Barrat
2016-03-15 4:09 ` Vaibhav Jain
2016-03-15 18:36 ` Frederic Barrat
2016-03-17 1:41 ` Ian Munsie
2016-03-17 2:45 ` Michael Neuling [this message]
2016-03-17 20:49 ` Frederic Barrat
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=1458182709.23128.5.camel@neuling.org \
--to=mikey@neuling.org \
--cc=fbarrat@linux.vnet.ibm.com \
--cc=imunsie@au1.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).