linux-kernel - Re: [PATCH][linux-next][RESEND] usb/gadget/pch

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Tue, 6 Mar 2012 06:58:17 -0800
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Tomoya MORINAGA <tomoya.rohm@...il.com>
Cc:	Felipe Balbi <balbi@...com>, linux-kernel@...r.kernel.org,
	linux-usb@...r.kernel.org, qi.wang@...el.com,
	yong.y.wang@...el.com, joel.clark@...el.com, kok.howg.ewe@...el.com
Subject: Re: [PATCH][linux-next][RESEND] usb/gadget/pch_udc: Fix compile error

On Tue, Mar 06, 2012 at 03:39:37PM +0900, Tomoya MORINAGA wrote:
> Hi
> 
> Add information.
> 
> My develop environment is on x86.
> 
> According to following report,
>   http://kisskb.ellerman.id.au/kisskb/buildresult/5771890/
>   http://kisskb.ellerman.id.au/kisskb/buildresult/5771905/
> 
> This occurred on sparc64.
> 
> I suspect this issue ins GPIO implementation for sparc64.
> Does sparc64 support GPIO interrupt ?
> (Even x86, before 2.6.39, GPIO interrupt is not implemented !)
> 
> Additionally, this driver is for companion chip of Intel Atom E6xx series.
> So, this driver is never used for except x86, e.g. sparc.

Then the Kconfig file should probably only enable it on x86 to prevent
these kinds of things :)

thanks,

greg k-h
--
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/