summaryrefslogtreecommitdiffstats
path: root/fs/ufs
diff options
context:
space:
mode:
authorGavin Shan <gwshan@linux.vnet.ibm.com>2016-05-03 15:41:36 +1000
committerMichael Ellerman <mpe@ellerman.id.au>2016-05-11 21:54:23 +1000
commit1e9167726c41b8d2126327379f4f82acbd548ba8 (patch)
tree67428118496b7810944031ceec8e7b98a3102b6b /fs/ufs
parent2b923ed1bd96cc471bb0f0eddfed6ae4753d717b (diff)
downloadop-kernel-dev-1e9167726c41b8d2126327379f4f82acbd548ba8.zip
op-kernel-dev-1e9167726c41b8d2126327379f4f82acbd548ba8.tar.gz
powerpc/powernv: Use PE instead of number during setup and release
In current implementation, the PEs that are allocated or picked from the reserved list are identified by PE number. The PE instance has to be picked according to the PE number eventually. We have same issue when PE is released. For pnv_ioda_pick_m64_pe() and pnv_ioda_alloc_pe(), this returns PE instance so that pnv_ioda_setup_bus_PE() can use the allocated or reserved PE instance directly. Also, pnv_ioda_setup_bus_PE() returns the reserved/allocated PE instance to be used in subsequent patches. On the other hand, pnv_ioda_free_pe() uses PE instance (not number) as its argument. No logical changes introduced. Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com> Reviewed-by: Alexey Kardashevskiy <aik@ozlabs.ru> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'fs/ufs')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud