From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751749AbdG0Smz (ORCPT ); Thu, 27 Jul 2017 14:42:55 -0400 Received: from mga06.intel.com ([134.134.136.31]:5407 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751598AbdG0Smx (ORCPT ); Thu, 27 Jul 2017 14:42:53 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.40,421,1496127600"; d="scan'208";a="883509108" Date: Thu, 27 Jul 2017 11:42:51 -0700 From: "Raj, Ashok" To: Casey Leedom Cc: Ding Tianhong , Alexander Duyck , Netdev , Bjorn Helgaas , "linux-arm-kernel@lists.infradead.org" , "David.Laight@aculab.com" , Alex Williamson , "l.stach@pengutronix.de" , "Suravee.Suthikulpanit@amd.com" , "catalin.marinas@arm.com" , "linux-pci@vger.kernel.org" , "will.deacon@arm.com" , Sinan Kaya , "robin.murphy@arm.com" , "linux-kernel@vger.kernel.org" , "davem@davemloft.net" , Ganesh GR , "asit.k.mallick@intel.com" , "jeffrey.t.kirsher@intel.com" , "mark.rutland@arm.com" , "gabriele.paoloni@huawei.com" , Michael Werner , "bhelgaas@google.com" , "patrick.j.cramer@intel.com" , "linuxarm@huawei.com" , "amira@mellanox.com" , "Bob.Shaw@amd.com" , ashok.raj@intel.com Subject: Re: [PATCH v7 2/3] PCI: Enable PCIe Relaxed Ordering if supported Message-ID: <20170727184251.GA205508@otc-nc-03> References: <67be791f-e0cf-8284-9229-17174dc741ef@codeaurora.org> <5f9b8bfb-41a8-a17c-6fea-581aec1d5573@huawei.com> <20170724090516.2e0f0d2a@w520.home> <2feff1a5-25b7-eb6c-7628-7c2257c56e95@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Casey > | Still no Intel and AMD guys has ack this, this is what I am worried about, > | should I ping some man again ? I can ack the patch set for Intel specific changes. Now that the doc is made public :-). Can you/Ding resend the patch series, i do have the most recent v7, some of the commit message wasn't easy to ready. Seems like this patch has gotten bigger than originally intended, but seems to be for the overall good :-). Sorry for staying silent up until now. Cheers, Ashok