Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752807AbbDBWIA (ORCPT ); Thu, 2 Apr 2015 18:08:00 -0400 Received: from mail-ig0-f181.google.com ([209.85.213.181]:33787 "EHLO mail-ig0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751186AbbDBWH6 (ORCPT ); Thu, 2 Apr 2015 18:07:58 -0400 MIME-Version: 1.0 In-Reply-To: <20150402.163715.643586069492103151.davem@davemloft.net> References: <1427857069-6789-1-git-send-email-yinghai@kernel.org> <20150402.163715.643586069492103151.davem@davemloft.net> Date: Thu, 2 Apr 2015 15:07:57 -0700 X-Google-Sender-Auth: 80sKhHrs4JF02VbOzcF729MQP3s Message-ID: Subject: Re: [PATCH 0/3] PCI/sparc: Fix booting with T5-8 From: Yinghai Lu To: David Miller , Bjorn Helgaas Cc: David Ahern , "linux-pci@vger.kernel.org" , "sparclinux@vger.kernel.org" , Linux Kernel Mailing List Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1130 Lines: 32 On Thu, Apr 2, 2015 at 1:37 PM, David Miller wrote: > From: Yinghai Lu > Date: Tue, 31 Mar 2015 19:57:46 -0700 > >> Fix regression by commit d63e2e1f3df9 ("sparc/PCI: Clip bridge windows to >> fit in upstream windows"). >> >> That cause bridge bar get clipped wrongly. >> >> The sparc64 dma_addr_t is 32-bit, we can not use it to check if we can >> use 64bit bar, introduce pci_bus_addr_t. >> >> sparc ofpci does not parse 64bit mem for root bus, add code to >> make sure that we get correct resource for root. >> >> Also there are device 64-bit res does not have pref bit flag, but bridges >> do have pref bit set, that cause extra "no compatible window". >> Set pref bit for them according to the errata. > > Just to be clear, who is going to merge this? :-) > Should be you or Bjorn, but one should get ack from another. Thanks Yinghai -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/