On Wed, 2018-02-28 at 17:08 -0600, Bjorn Helgaas wrote:
>
> What's the bottom line? Do we want this for sparc? If so, do you
> want to take it, Dave M, or would you like me to?
I need to fix it first, and then the intention is for Dave to take it.
There'll be a final patch to remove ARCH_GENER
From: Bjorn Helgaas
Date: Wed, 28 Feb 2018 17:08:29 -0600
> On Mon, Feb 19, 2018 at 10:30:25AM -0500, David Miller wrote:
>> From: David Woodhouse
>> Date: Mon, 19 Feb 2018 15:24:18 +
>>
>> >> For one, the sparc specific code allows mmap'ing any address range
>> >> within a PCI bus device.
On Mon, Feb 19, 2018 at 10:30:25AM -0500, David Miller wrote:
> From: David Woodhouse
> Date: Mon, 19 Feb 2018 15:24:18 +
>
> >> For one, the sparc specific code allows mmap'ing any address range
> >> within a PCI bus device. The generic code does not allow that.
> >
> >
> > You mean any a
From: David Woodhouse
Date: Mon, 19 Feb 2018 15:24:18 +
>> For one, the sparc specific code allows mmap'ing any address range
>> within a PCI bus device. The generic code does not allow that.
>
>
> You mean any address range in a given PCI bus even if there is no
> actual device with a BAR
On Mon, 2018-02-19 at 09:49 -0500, David Miller wrote:
> From: David Woodhouse
> Date: Mon, 19 Feb 2018 13:04:12 +
>
> >
> > Commit f719582435 ("PCI: Add pci_mmap_resource_range() and use it for
> > ARM64") added this generic function with the intent of using it
> > everywhere and ultimately
From: David Woodhouse
Date: Mon, 19 Feb 2018 13:04:12 +
> Commit f719582435 ("PCI: Add pci_mmap_resource_range() and use it for
> ARM64") added this generic function with the intent of using it
> everywhere and ultimately killing the old arch-specific implementations.
>
> Let's get on with t
6 matches
Mail list logo
