From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753296AbcAOCXI (ORCPT ); Thu, 14 Jan 2016 21:23:08 -0500 Received: from mail-bn1on0075.outbound.protection.outlook.com ([157.56.110.75]:4126 "EHLO na01-bn1-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753219AbcAOCXG (ORCPT ); Thu, 14 Jan 2016 21:23:06 -0500 From: "Yu, Xiangliang" To: Allen Hubbe , "jdmason@kudzu.us" , "dave.jiang@intel.com" , "linux-ntb@googlegroups.com" , "linux-kernel@vger.kernel.org" CC: SPG_Linux_Kernel Subject: RE: [PATCH V3 0/2] AMD NTB V3 changes Thread-Topic: [PATCH V3 0/2] AMD NTB V3 changes Thread-Index: AQHRTpcz7ukqIKJppEyizEuPy6HBlp77Ks+AgACslFA= Date: Fri, 15 Jan 2016 02:23:02 +0000 Message-ID: References: <1452771830-16907-1-git-send-email-Xiangliang.Yu@amd.com> <000001d14ee3$ffd532c0$ff7f9840$@emc.com> In-Reply-To: <000001d14ee3$ffd532c0$ff7f9840$@emc.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=Xiangliang.Yu@amd.com; x-originating-ip: [210.13.97.168] x-microsoft-exchange-diagnostics: 1;BLUPR12MB0420;5:F0bafMrd92bPeMeLiDW8Lg5duL2mExoez7OEIf47LByNEeRXzN0PhYfFAGtt3uDHC7mWDJNPfegimJZlW5Sglim0O/tkJdHj5PBk1sWFfE2GSr80tDJ+cBmExivFGZrlrRlEuxcJuYJ/Uob12cgltg==;24:aIP8cdyEm1/zqcEIjZkUR4m54EZBy1XOjieITHfs8ueyTYlJcPayY4ylbcZ2VVioEVyo5eT5mDAXL/pViBBuu/91Tc69ZO+5HClKYKr26MY=;20:yXl8jGpngGITQHiVDqUTsV2RJ1Cc9ehb23BTlPFYKgHC5YktFYqIg3JwiR9JEVwU2DjfUuEAAlDUwTPzYOPqdUlKllc5Q+d7pgxbtc2eV5z255JxHt/DEg2PBUUliB74lWD3FMd6YI4mqTC7RuQ0kjtFcr033nS9btZ1QQtERwJu8eOHArAXsNJK8h+QHonzg1kdDtkX8ycmE66uTbkrWeR5vc/2lgr+VPthsj8tdpViJ1gsA//ioaRnO2bRPXcx x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR12MB0420; x-ms-office365-filtering-correlation-id: 92d61b54-a820-4dad-7a6c-08d31d52cb5d x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(767451399110); x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(601004)(2401047)(520078)(8121501046)(5005006)(10201501046)(3002001);SRVR:BLUPR12MB0420;BCL:0;PCL:0;RULEID:;SRVR:BLUPR12MB0420; x-forefront-prvs: 08220FA8D6 x-forefront-antispam-report: SFV:NSPM;SFS:(10009020)(6009001)(199003)(189002)(76176999)(5004730100002)(101416001)(74316001)(81156007)(122556002)(92566002)(2201001)(1096002)(1220700001)(40100003)(11100500001)(2900100001)(2950100001)(3846002)(86362001)(77096005)(5002640100001)(19580395003)(586003)(10400500002)(102836003)(19580405001)(5003600100002)(6116002)(50986999)(99286002)(66066001)(97736004)(54356999)(106116001)(76576001)(106356001)(5008740100001)(5001960100002)(33656002)(5001770100001)(189998001)(87936001)(2906002)(105586002)(2501003)(4326007)(7059030)(217873001);DIR:OUT;SFP:1101;SCL:1;SRVR:BLUPR12MB0420;H:BLUPR12MB0420.namprd12.prod.outlook.com;FPR:;SPF:None;PTR:InfoNoRecords;A:1;MX:1;LANG:en; Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 X-OriginatorOrg: amd.com X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Jan 2016 02:23:02.1733 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 3dd8961f-e488-4e60-8e11-a82d994e183d X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR12MB0420 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id u0F2NEq9026774 > > From: Xiangliang Yu > > > > 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. Actually, I have answered the question in V2 comments. Now again, I want to submitted all power management related code if runtime part is ready. > 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. I want to add flush function into ntb_transport.c, but I can't verify the implementation Because hardware is not ready. So I just define a interface this time for future use. I notice there are lot of interface that hasn't been used in ntb.h.