linux-kernel - Re: [PATCH v4 01/23] mfd: omap-usb-host: get rid of cpu_is

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20121214005450.GO26699@sortiz-mobl>
Date:	Fri, 14 Dec 2012 01:54:50 +0100
From:	Samuel Ortiz <sameo@...ux.intel.com>
To:	Tony Lindgren <tony@...mide.com>
Cc:	balbi@...com, paul@...an.com, keshava_mgowda@...com,
	sshtylyov@...sta.com, bjorn@...k.no, linux-usb@...r.kernel.org,
	linux-omap@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org, Roger Quadros <rogerq@...com>
Subject: Re: [PATCH v4 01/23] mfd: omap-usb-host: get rid of cpu_is_omap..()
 macros

Hi Tony,

On Thu, Dec 13, 2012 at 01:49:49PM -0800, Tony Lindgren wrote:
> Hi Samuel,
> 
> * Roger Quadros <rogerq@...com> [121210 02:23]:
> > Instead of using cpu_is_omap..() macros in the device driver we
> > rely on information provided in the platform data.
> > 
> > The only information we need is whether the USB Host module has
> > a single ULPI bypass control bit for all ports or individual bypass
> > control bits for each port. OMAP3 REV2.1 and earlier have the former.
> 
> I'd like to apply this patch as a fix so I can finally nuke plat/cpu.h
> for omaps by -rc1 before more drivers start using it again.
> 
> That is assuming nobody else is planning on merging this series for
> v3.8 presumably. 
This should go into 3.9, yes.


> Want to ack this one?
Looks fine to me:
Acked-by: Samuel Ortiz <sameo@...ux.intel.com>

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/
--
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/