linux-kernel - Re: [PATCH] mfd: omap-usb-host: Fix improper mask use

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]

Date:	Tue, 29 Jul 2014 16:10:42 +0100
From:	Lee Jones <lee.jones@...aro.org>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	Michael Welling <mwelling@...cinc.com>,
	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
	rogerq@...com, stern@...land.harvard.edu, balbi@...com,
	stable@...r.kernel.org
Subject: Re: [PATCH] mfd: omap-usb-host: Fix improper mask use

On Tue, 29 Jul 2014, Greg KH wrote:

> On Tue, Jul 29, 2014 at 09:33:25AM +0100, Lee Jones wrote:
> > single-ulpi-bypass is a flag used for older OMAP3 silicon.
> > 
> > The flag when set, can excite code that improperly uses the
> > OMAP_UHH_HOSTCONFIG_UPLI_BYPASS define to clear the corresponding bit.
> > Instead it clears all of the other bits disabling all of the ports in
> > the process.
> > 
> > Signed-off-by: Michael Welling <mwelling@...cinc.com>
> > ---
> > 
> > --> Applied, thanks. <--
> > 
> >  drivers/mfd/omap-usb-host.c |    2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> <formletter>
> 
> This is not the correct way to submit patches for inclusion in the
> stable kernel tree.  Please read Documentation/stable_kernel_rules.txt
> for how to do this properly.
> 
> </formletter>

It was worth a try. ;)

Patch queued for MFD -next and 'Cc: stable@...r.kernel.org' tag added.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
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/