linux-kernel - Re: [PATCH -next] net: hisilicon: Never build on SPARC

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] [day] [month] [year] [list]

Message-ID: <563D52D4.2020607@roeck-us.net>
Date:	Fri, 6 Nov 2015 17:24:36 -0800
From:	Guenter Roeck <linux@...ck-us.net>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH -next] net: hisilicon: Never build on SPARC

On 11/06/2015 12:30 PM, Arnd Bergmann wrote:
> On Friday 06 November 2015 11:16:52 Guenter Roeck wrote:
>> On Wed, Oct 21, 2015 at 02:53:20PM -0700, Guenter Roeck wrote:
>>> On Wed, Oct 21, 2015 at 09:11:53PM +0200, Arnd Bergmann wrote:
>>>> On Wednesday 21 October 2015 10:03:05 Guenter Roeck wrote:
>>>>> Anyway, if it gets that complicated, I think we should stick with
>>>>> just returning OF_BAD_ADDR. The above really suggests the need for
>>>>> an architecture specific solution.
>>>>
>>>> Probably no harm in this really: the far more common
>>>> of_address_to_resource() and of_iomap() helpers are equally
>>>> broken on SPARC and we just return a runtime error for those
>>>> as well without CONFIG_OF_ADDRESS rather than breaking the build.
>>>>
>>> Agreed. Given this, returning OF_BAD_ADDR sounds like a better choice.
>>>
>> Arnd,
>>
>> do you know if a fix for this problem is pending in some branch ?
>> Mainline sparc builds are now affected.
>>
>
> I don't think anyone wrote the patch to do this. Can you send one?
>

I'll see what I can do.

Guenter


--
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/