linux-kernel - Re: spi/bcm63xx: unknown CONFIG_BIG

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: <55F7CB6E.1090008@openwrt.org>
Date:	Tue, 15 Sep 2015 09:40:30 +0200
From:	Jonas Gorski <jogo@...nwrt.org>
To:	Valentin Rothberg <valentinrothberg@...il.com>
Cc:	broonie@...nel.org, Paul Bolle <pebolle@...cali.nl>,
	ziegler@...fau.de, linux-kernel@...r.kernel.org
Subject: Re: spi/bcm63xx: unknown CONFIG_BIG_ENDIAN

Hi Valentin,

On 15.09.2015 08:24, Valentin Rothberg wrote:
> Hi Jonas,
> 
> your commit 158fcc4e050a ("spi/bcm63xx: replace custom io accessors with
> standard ones") has shown up in today's Linux next tree (i.e.,
> next-20150915).  
> 
> This commit adds four #ifdef blocks depending on CONFIG_BIG_ENDIAN,
> which is not defined in Kconfig breaking the #ifdef #else conditions.
> 
> Is there a patch queued somewhere to add this option to Kconfig?  
> 
> I found some other candidates like '__BIG_ENDIAN' which is used in other
> drivers, or 'CPU_BIG_ENDIAN' which is defined for mips.  Maybe they can
> be used instead.

You are right, and I had fixed this in my V2 patchset from saturday, but
appearently this wasn't fast enough.
Mark? If you can drop patches 2 to 4 that would be easiest for me, but if
you don't do rebases on your for-next branch, then I'll rewrite the
patches to apply on top of the already applied old versions and send a v3.


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