From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754818Ab3I1DGZ (ORCPT ); Fri, 27 Sep 2013 23:06:25 -0400 Received: from gate.crashing.org ([63.228.1.57]:60640 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754557Ab3I1DGS (ORCPT ); Fri, 27 Sep 2013 23:06:18 -0400 Message-ID: <1380337550.27811.71.camel@pasglop> Subject: Re: Please revert 928bea964827d7824b548c1f8e06eccbbc4d0d7d From: Benjamin Herrenschmidt To: Yinghai Lu Cc: Linus Torvalds , Bjorn Helgaas , "linux-pci@vger.kernel.org" , linuxppc-dev , Linux Kernel list , "Rafael J. Wysocki" Date: Sat, 28 Sep 2013 13:05:50 +1000 In-Reply-To: References: <1380270519.27811.10.camel@pasglop> <1380318405.27811.37.camel@pasglop> <1380321480.27811.53.camel@pasglop> <1380323960.27811.67.camel@pasglop> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.6.4-0ubuntu1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2013-09-27 at 16:44 -0700, Yinghai Lu wrote: > > Thus the port driver bails out before calling pci_set_master(). The fix > > is to call pci_set_master() unconditionally. However that lead me to > > find to a few interesting oddities in that port driver code: > > can we revert that partially change ? aka we should check get_port.... > at first... > > like attached. In the meantime, can you properly submit the other one with the warning to Linus ? It will make things more robust overall... Also, please read my other comments. I think we are treading on very fragile ground with that whole business of potentially disabling bridges in the pcieport driver ... Cheers, Ben.