linux-kernel - RE: [PATCH V5 1/1] NTB: Add support for AMD PCI-Express Non-Transparent Bridge

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: <BLUPR12MB0420FE127B3F3035FF465D95EBC30@BLUPR12MB0420.namprd12.prod.outlook.com>
Date:	Thu, 21 Jan 2016 04:21:30 +0000
From:	"Yu, Xiangliang" <Xiangliang.Yu@....com>
To:	"Hubbe, Allen" <Allen.Hubbe@....com>,
	"jdmason@...zu.us" <jdmason@...zu.us>,
	"dave.jiang@...el.com" <dave.jiang@...el.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-ntb@...glegroups.com" <linux-ntb@...glegroups.com>
CC:	SPG_Linux_Kernel <SPG_Linux_Kernel@....com>
Subject: RE: [PATCH V5 1/1] NTB: Add support for AMD PCI-Express
 Non-Transparent Bridge

> -----Original Message-----
> From: Hubbe, Allen [mailto:Allen.Hubbe@....com]
> Sent: Thursday, January 21, 2016 11:54 AM
> To: Yu, Xiangliang; jdmason@...zu.us; dave.jiang@...el.com; linux-
> kernel@...r.kernel.org; linux-ntb@...glegroups.com
> Cc: SPG_Linux_Kernel
> Subject: RE: [PATCH V5 1/1] NTB: Add support for AMD PCI-Express Non-
> Transparent Bridge
> 
> From: Xiangliang Yu [mailto:Xiangliang.Yu@....com]
> > This adds support for AMD's PCI-Express Non-Transparent Bridge
> > (NTB) device on the Zeppelin platform. The driver connnects to the
> > standard NTB sub-system interface, with modification to add hooks for
> > power management in a separate patch. The AMD NTB device has 3
> memory
> > windows, 16 doorbell, 16 scratch-pad registers, and supports up to 16
> > PCIe lanes running a Gen3 speeds.
> >
> > Signed-off-by: Xiangliang Yu <Xiangliang.Yu@....com>
> 
> 
> > Signed-off-by: Jon Mason <jdmason@...zu.us>
> > Signed-off-by: Allen Hubbe <Allen.Hubbe@....com>
> 
> Hold on a sec... what?  Who?  I don't remember signing off on this.
> 
> Signed-off-by has legal implications with regards to the developer certificate
> of origin.  Please don't just put names on stuff!  It's forgery!

Please help change it to reviewer-by when applying it. Thanks!