* Nicholas Krause <xerofoify@xxxxxxxxx> [140702 18:33]:
> This removes the FIXME message above ocpi_enable being declared
> for proper locking in this function. As of the current kernel
> verisons there is no need for locking as only one driver uses
> this function currently and therefore there is no need for real
> locking requirements.
>
> Signed-off-by: Nicholas Krause <xerofoify@xxxxxxxxx>
Thanks applying into omap-for-v3.17/fixes-not-urgent.
Tony
> ---
> arch/arm/mach-omap1/ocpi.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/arm/mach-omap1/ocpi.c b/arch/arm/mach-omap1/ocpi.c
> index 238170c..44a3d19 100644
> --- a/arch/arm/mach-omap1/ocpi.c
> +++ b/arch/arm/mach-omap1/ocpi.c
> @@ -55,7 +55,6 @@ static struct clk *ocpi_ck;
>
> /*
> * Enables device access to OMAP buses via the OCPI bridge
> - * FIXME: Add locking
> */
> int ocpi_enable(void)
> {
> --
> 1.9.1
>
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
