linux-kernel - Re: [MeeGo-Dev][PATCH] Topcliff: Update 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:	Fri, 3 Sep 2010 09:17:58 +0900
From:	"Masayuki Ohtake" <masa-korg@....okisemi.com>
To:	"Greg KH" <gregkh@...e.de>
Cc:	"Greg KH" <greg@...ah.com>, <meego-dev@...go.com>,
	"LKML" <linux-kernel@...r.kernel.org>, <yong.y.wang@...el.com>,
	<qi.wang@...el.com>, <andrew.chih.howe.khor@...el.com>,
	<arjan@...ux.intel.com>, <alan@...ux.intel.com>,
	<margie.foster@...el.com>,
	"Tomoya MORINAGA" <morinaga526@....okisemi.com>
Subject: Re: [MeeGo-Dev][PATCH] Topcliff: Update PCH_PHUB driver to 2.6.35

Hi Greg,

I understand.
Since we have only 32-bit kernel, we couldn't see the WARNINGs.

Thanks, Ohtake(OKISemi)

----- Original Message ----- 
From: "Greg KH" <gregkh@...e.de>
To: "Masayuki Ohtake" <masa-korg@....okisemi.com>
Cc: "Greg KH" <greg@...ah.com>; <meego-dev@...go.com>; "LKML" <linux-kernel@...r.kernel.org>; <yong.y.wang@...el.com>;
<qi.wang@...el.com>; <andrew.chih.howe.khor@...el.com>; <arjan@...ux.intel.com>; <alan@...ux.intel.com>;
<margie.foster@...el.com>; "Tomoya MORINAGA" <morinaga526@....okisemi.com>
Sent: Thursday, September 02, 2010 10:18 PM
Subject: Re: [MeeGo-Dev][PATCH] Topcliff: Update PCH_PHUB driver to 2.6.35


> On Thu, Sep 02, 2010 at 03:38:11PM +0900, Masayuki Ohtake wrote:
> > Hi Greg,
> >
> > > Nope, I still get a warning with this patch, but I'll go fix it up:
> >
> > To see your indicated warning information,
> > I have tried to build the following(latest) version with our phub patch.
> >   - linux-2.6.35.4
> >   - linux-2.6.35.y
> >
> > But we can't see the warning(No warning No error).
> > How can we see the warning ?
>
> Build it on a x86-64 kernel.  The issue was the 64bit size of a pointer
> and the ssize_t variable.  My fix solved these issues for both the 32
> and 64bit kernels.
>
> 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/