Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755680AbbBFRx7 (ORCPT ); Fri, 6 Feb 2015 12:53:59 -0500 Received: from mail-ie0-f178.google.com ([209.85.223.178]:38526 "EHLO mail-ie0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755076AbbBFRx5 (ORCPT ); Fri, 6 Feb 2015 12:53:57 -0500 MIME-Version: 1.0 In-Reply-To: <54D4DD95.7000303@ti.com> References: <1423173179-10227-1-git-send-email-m-karicheri2@ti.com> <20150206151542.GD23190@e104818-lin.cambridge.arm.com> <54D4DD95.7000303@ti.com> From: Bjorn Helgaas Date: Fri, 6 Feb 2015 11:53:35 -0600 Message-ID: Subject: Re: [PATCH v6 0/7] PCI: get DMA configuration from parent device To: Murali Karicheri Cc: Catalin Marinas , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "iommu@lists.linux-foundation.org" , "devicetree@vger.kernel.org" , "linux-pci@vger.kernel.org" , Russell King , Arnd Bergmann , Joerg Roedel , Will Deacon , Rob Herring , "suravee.suthikulpanit@amd.com" , "grant.likely@linaro.org" 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: 1551 Lines: 36 On Fri, Feb 6, 2015 at 9:28 AM, Murali Karicheri wrote: > On 02/06/2015 10:15 AM, Catalin Marinas wrote: >> >> On Thu, Feb 05, 2015 at 09:52:52PM +0000, Murali Karicheri wrote: >>> >>> This patch add an important capability to PCI driver on Keystone. I hope >>> to >>> have this merged to the upstream branch so that it is available for >>> v3.20. >> >> It's very late for 3.20 and the code hasn't been in linux-next at all >> (but it's not me who's merging this code), unless you can squeeze it in >> as a bug-fix. > > This is in fact a bug fix as PCI on Keystone is broken without this. Oh, sorry, I didn't realize that this was so urgent. I guess I read "this adds an important capability" in the cover letter and concluded that it was new functionality. Anyway, if it's broken, presumably PCI on Keystone *did* work at one point. Can you identify the commit that broke it and requires these fixes, so we can figure out how far the fixes need to be backported? If I merge it, I would like to get into my for-linus branch and get a little time in -next before asking Linus to pull it. The merge window is a little wrinkle there -- I don't like to add new things to the mix during the window. But if it's an important fix we can still get it in before the final v3.20. Bjorn -- 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/