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: <000001d14ee3$ffd532c0$ff7f9840$@emc.com>
Date:	Thu, 14 Jan 2016 10:55:31 -0500
From:	"Allen Hubbe" <Allen.Hubbe@....com>
To:	"'Xiangliang Yu'" <Xiangliang.Yu@....com>, <jdmason@...zu.us>,
	<dave.jiang@...el.com>, <linux-ntb@...glegroups.com>,
	<linux-kernel@...r.kernel.org>
Cc:	<SPG_Linux_Kernel@....com>
Subject: RE: [PATCH V3 0/2] AMD NTB V3 changes

> From: Xiangliang Yu <Xiangliang.Yu@....com>
> 
> Main changes in V3
> 1. Remove all power managment related code.

Can you send the third patch with the power management code?  I think it is important functionality.

Furthermore, a review of the power management patch will help with getting the flush patch accepted.  If the power management patch is reviewed and acked as is, the flush patch is probably ok, too, as is.  If there are changes to power management that are also applicable to the flush patch, it would be good to keep it all consistent when adding the functionality to the api.

> 2. Put makefile and kconfig changes in first patch.
> 3. Call readl/writel directly, not use macros to hide it.

I think this is almost ready.  See comments in NTB: Add AMD PCI-Express NTB driver.

Allen

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ