From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754684AbbIHJzK (ORCPT ); Tue, 8 Sep 2015 05:55:10 -0400 Received: from mail-oi0-f46.google.com ([209.85.218.46]:33704 "EHLO mail-oi0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753369AbbIHJzH (ORCPT ); Tue, 8 Sep 2015 05:55:07 -0400 MIME-Version: 1.0 In-Reply-To: References: <1440807447-584-1-git-send-email-mcgrof@do-not-panic.com> <3544271.GfynADMPqZ@wuerfel> <20150903014415.GQ8051@wotan.suse.de> From: "Luis R. Rodriguez" Date: Tue, 8 Sep 2015 02:54:47 -0700 X-Google-Sender-Auth: ktjRKs43yTQqKp6oarPkzg0Oh3c Message-ID: Subject: Re: [RFC] asm-generic/pci_iomap.h: make custom PCI BAR requirements explicit To: Arnd Bergmann Cc: "Luis R. Rodriguez" , linux-arch@vger.kernel.org, Ingo Molnar , schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com, linux-s390@vger.kernel.org, Borislav Petkov , Guenter Roeck , "linux-kernel@vger.kernel.org" , Andrew Morton , Steven Rostedt Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Sep 2, 2015 at 6:47 PM, Luis R. Rodriguez wrote: > On Wed, Sep 2, 2015 at 6:44 PM, Luis R. Rodriguez wrote: >>> I don't think we really need to spell it out here. s390 PCI is different >>> from everybody else's in a lot of ways, so a simple 'depends on PCI && >>> !S390' for CONFIG_PCI_IOMAP seems simpler and more intuitive. >> >> Sure that would work as well. > > But on second thought it still would leave us reactive to S390, this > solution would get folks extending this asm-generic stuff to also have > something in place for S390, even if its just returning NULL. Arnd, thoughts? Luis