linux-kernel - Re: [PATCH] omap16xx: Removes fixme no longer needed in ocpi

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20140708081606.GC28884@atomide.com>
Date:	Tue, 8 Jul 2014 01:16:07 -0700
From:	Tony Lindgren <tony@...mide.com>
To:	Nicholas Krause <xerofoify@...il.com>
Cc:	linux@....linux.org.uk, linux-omap@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] omap16xx: Removes fixme no longer needed in ocpi_enable()

* Nicholas Krause <xerofoify@...il.com> [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@...il.com>

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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/