linux-kernel - Re: [PATCH 0/3] PCI/sparc: Fix booting with T5-8

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAE9FiQV8=tGiPJ0qEJvMBAzk-i2aubmQhkNoa-Gei9y7SXiubw@mail.gmail.com>
Date:	Thu, 2 Apr 2015 15:07:57 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	David Miller <davem@...emloft.net>,
	Bjorn Helgaas <bhelgaas@...gle.com>
Cc:	David Ahern <david.ahern@...cle.com>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	"sparclinux@...r.kernel.org" <sparclinux@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/3] PCI/sparc: Fix booting with T5-8

On Thu, Apr 2, 2015 at 1:37 PM, David Miller <davem@...emloft.net> wrote:
> From: Yinghai Lu <yinghai@...nel.org>
> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/