diff options
| author | Gavin Shan <gwshan@linux.vnet.ibm.com> | 2015-03-27 11:22:17 +1100 |
|---|---|---|
| committer | Benjamin Herrenschmidt <benh@kernel.crashing.org> | 2015-03-31 13:10:39 +1100 |
| commit | 433185d2b4e9c25f2a444424c05af72fbadd4275 (patch) | |
| tree | 8890e9a7b5560458bdb9d2694b8f0f39633ed5e7 /arch/metag/boot | |
| parent | c6406d8fbb014bebdfb5bf3c244548958aec7379 (diff) | |
| download | linux-433185d2b4e9c25f2a444424c05af72fbadd4275.tar.gz linux-433185d2b4e9c25f2a444424c05af72fbadd4275.tar.bz2 linux-433185d2b4e9c25f2a444424c05af72fbadd4275.zip | |
powerpc/eeh: Fix PE#0 check in eeh_add_to_parent_pe()
The function eeh_add_parent_pe() is used to create a PE or add one
edev to its parent PE. Current code checks if PE#0 is valid for the
later case. Actually, we should validate PE#0 for both cases when
EEH core regards PE#0 as invalid one (without flag EEH_VALID_PE_ZERO).
Otherwise, not all EEH devices can be added to its parent PE#0 for
EEH on P7IOC.
The patch fixes the issue by validating PE#0 for the two cases. So far,
we don't have PE#0 for EEH on P7IOC, but it will show up when we enable
M64 for P7IOC. The patch also makes the error message more meaningful.
Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Diffstat (limited to 'arch/metag/boot')
0 files changed, 0 insertions, 0 deletions