Patch "powerpc/powernv: Don't warn on PE init if unfreeze is unsupported" has been added to the 4.9-stable tree

This is a note to let you know that I've just added the patch titled

powerpc/powernv: Don't warn on PE init if unfreeze is unsupported

to the 4.9-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
powerpc-powernv-don-t-warn-on-pe-init-if-unfreeze-is-unsupported.patch
and it can be found in the queue-4.9 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.

From: Russell Currey <[email protected]>
Date: Wed, 16 Nov 2016 12:12:26 +1100
Subject: powerpc/powernv: Don't warn on PE init if unfreeze is unsupported

From: Russell Currey <[email protected]>

commit d4791db527bf397c84c9956c3ece9692ed5322ac upstream.

Whenever a PE is initialised in powernv, opal_pci_eeh_freeze_clear() is called. This is to remove any existing freeze, and has no negative side effects if the PE is already in an unfrozen state. On PHB backends that don't support this operation and return OPAL_UNSUPPORTED, this creates a scary and misleading warning message.

Skip the warning message on init if OPAL_UNSUPPORTED is returned.

As far as I'm aware, this currently only affects NPUs.

---
 arch/powerpc/platforms/powernv/pci-ioda.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

@@ -145,7 +145,7 @@ static struct pnv_ioda_pe *pnv_ioda_init
 	 */
 	rc = opal_pci_eeh_freeze_clear(phb->opal_id, pe_no,
 				       OPAL_EEH_ACTION_CLEAR_FREEZE_ALL);
-	if (rc != OPAL_SUCCESS)
+	if (rc != OPAL_SUCCESS && rc != OPAL_UNSUPPORTED)
 		pr_warn("%s: Error %lld unfreezing PHB#%d-PE#%d\n",
 			__func__, rc, phb->hose->global_number, pe_no);
 

Patches currently in stable-queue which might be from [email protected] are

queue-4.9/powerpc-powernv-don-t-warn-on-pe-init-if-unfreeze-is-unsupported.patch