All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Ivan Mikhaylov <ivan@de.ibm.com>,
	Alistair Popple <alistair@popple.id.au>,
	Matt Porter <mporter@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Joel Stanley <joel@jms.id.au>, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 4/4] arch/powerpc/44x/fsp2: wdt tcr update instead of whole rewrite
Date: Tue, 23 May 2017 14:09:46 +1000	[thread overview]
Message-ID: <87lgpo8b91.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20170519154705.10504-1-ivan@de.ibm.com>

Ivan Mikhaylov <ivan@de.ibm.com> writes:
>
> From my point of view it's possible. I've checked docu and on idea
> it should be possible cause WP is only affecting watchdog ping time.

The question is, is there any chance that leaving those bits set on
another platform will cause a problem?

ie. on existing machines we always clear those bits, is it OK that we
will now start leaving those bits with whatever value they had.

cheers

  reply	other threads:[~2017-05-23  4:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-15 13:07 [PATCH 4/4] arch/powerpc/44x/fsp2: wdt tcr update instead of whole rewrite Ivan Mikhaylov
2017-05-19 10:24 ` Michael Ellerman
2017-05-19 10:24   ` Michael Ellerman
2017-05-19 15:47   ` Ivan Mikhaylov
2017-05-19 15:47     ` Ivan Mikhaylov
2017-05-23  4:09     ` Michael Ellerman [this message]
2017-05-26 10:37       ` Michael Ellerman
2017-05-30  9:11     ` [4/4] " Michael Ellerman
2017-05-19 10:30 ` [PATCH 4/4] " Benjamin Herrenschmidt

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=87lgpo8b91.fsf@concordia.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=alistair@popple.id.au \
    --cc=benh@kernel.crashing.org \
    --cc=ivan@de.ibm.com \
    --cc=joel@jms.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mporter@kernel.crashing.org \
    --cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.