Re: [PATCH 1/2] net/fsl_pq_mdio: check TBI address for consistency with mapped range

Gerlando Falauto wrote: Change-Id: If1e7d8931f440ea9259726c36d3df797dda016fb You need to remove these from patches that are emailed, and fix the pointer type comparison. Otherwise, Acked-by: Timur Tabi -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body

Re: [PATCH 1/2] net/fsl_pq_mdio: check TBI address for consistency with mapped range

Gerlando Falauto wrote: Change-Id: If1e7d8931f440ea9259726c36d3df797dda016fb You need to remove these from patches that are emailed, and fix the pointer type comparison. Otherwise, Acked-by: Timur Tabi -- To unsubscribe from this list: send the line "unsubscribe

Re: [PATCH 1/2] net/fsl_pq_mdio: check TBI address for consistency with mapped range

Hi Gerlando, [auto build test WARNING on net/master -- if it's inappropriate base, please ignore] config: powerpc-tqm8541_defconfig (attached as .config) reproduce: wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross

[PATCH 1/2] net/fsl_pq_mdio: check TBI address for consistency with mapped range

When configuring the MDIO subsystem it is also necessary to configure the TBI register. Make sure the TBI is contained within the mapped register range in order to: a) make sure the address is computed correctly b) make users aware that we're actually accessing that register In case of error,

Re: [PATCH 1/2] net/fsl_pq_mdio: check TBI address for consistency with mapped range

Hi Gerlando, [auto build test WARNING on net/master -- if it's inappropriate base, please ignore] config: powerpc-tqm8541_defconfig (attached as .config) reproduce: wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross

[PATCH 1/2] net/fsl_pq_mdio: check TBI address for consistency with mapped range

When configuring the MDIO subsystem it is also necessary to configure the TBI register. Make sure the TBI is contained within the mapped register range in order to: a) make sure the address is computed correctly b) make users aware that we're actually accessing that register In case of error,