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]

Message-ID: <D5AB6E638E5A3E4B8F4406B113A5A19A2A56E877@shsmsx501.ccr.corp.intel.com>
Date:	Fri, 3 Sep 2010 09:13:43 +0800
From:	"Wang, Qi" <qi.wang@...el.com>
To:	Greg KH <gregkh@...e.de>
CC:	Greg KH <greg@...ah.com>,
	"meego-dev@...go.com" <meego-dev@...go.com>,
	LKML <linux-kernel@...r.kernel.org>,
	"Wang, Yong Y" <yong.y.wang@...el.com>,
	"Khor, Andrew Chih Howe" <andrew.chih.howe.khor@...el.com>,
	"arjan@...ux.intel.com" <arjan@...ux.intel.com>,
	"alan@...ux.intel.com" <alan@...ux.intel.com>,
	"Foster, Margie" <margie.foster@...el.com>,
	Tomoya MORINAGA <morinaga526@....okisemi.com>,
	Masayuki Ohtake <masa-korg@....okisemi.com>
Subject: RE: [MeeGo-Dev][PATCH] Topcliff: Update PCH_PHUB driver to 2.6.35

Hi Greg KH,

When all the drivers are accepted by the upstream, our source-forge is useless. Currently it's a temporary site for us to smoke test the driver quality.

Best Regards,
Qi.

> -----Original Message-----
> From: Greg KH [mailto:gregkh@...e.de]
> Sent: Thursday, September 02, 2010 9:19 PM
> To: Masayuki Ohtake
> Cc: Wang, Qi; Greg KH; meego-dev@...go.com; LKML; Wang, Yong Y; Khor,
> Andrew Chih Howe; arjan@...ux.intel.com; alan@...ux.intel.com; Foster,
> Margie; Tomoya MORINAGA
> Subject: Re: [MeeGo-Dev][PATCH] Topcliff: Update PCH_PHUB driver to 2.6.35
> 
> On Thu, Sep 02, 2010 at 03:44:00PM +0900, Masayuki Ohtake wrote:
> > Hi Qi-san
> >
> > I will sync this phub patch to source-forge by today.
> 
> You are going to delete this version when the driver is merged into the
> kernel tree, right?  Please don't try to maintain the code external to
> the kernel, that never works properly.
> 
> thanks,
> 
> greg k-h