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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 24 Aug 2014 16:38:39 +0800
From:	Chen Gang <>
To:	Ralf Baechle <>
CC:	Arnd Bergmann <>,,,,,, Geert Uytterhoeven <>,
	Jean Delvare <>,,,,,,,,,,,,,,,,, Michal Simek <>,,,,,
	Benjamin Herrenschmidt <>,,,
	Martin Schwidefsky <>,, Liqin Chen <>,
	Lennox Wu <>,
	"David S. Miller" <>,,, Richard Weinberger <>,,,,,,,,,,
	"" <>,,,,,,,,,,,,,,,,,,,,,,
Subject: Re: [PATCH v3] arch: Kconfig: Let all architectures set endian explicitly

Hello Maintainers:

Is this patch OK? If it pass basic checking, please let me know, and I
shall try to make another related patch for KBuild (I can do nothing
related with Kbuild, before get confirmation for this patch).


On 8/15/14 17:01, Chen Gang wrote:
> On 8/15/14 6:14, Chen Gang wrote:
>> On 08/15/2014 02:04 AM, Ralf Baechle wrote:
>> OK, thanks, I assumes when support both endian, the default choice is
>> CPU_BIG_ENDIAN, although no default value for choice (originally, I did
>> worry about it).
>>> So I think you can just drop the MIPS segment from your patch.
>> If what I assumes is correct, what you said sounds reasonable to me.
> So for me, it is harmless to add CPU_*_ENDIAN explicitly, and can let
> other members don't need think of.
> By the way, for sh, it is almost the same case, except it contents the
> default value, for me, it is clear enough, so I skip sh architecture in
> this patch.
> Thanks

Chen Gang

Open, share, and attitude like air, water, and life which God blessed
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists