Re: [PATCH v3] arch: Kconfig: Let all architectures set endian explicitly
From: Vineet Gupta <hidden>
Date: 2014-08-14 23:14:04
Also in:
linux-alpha, linux-mips, linux-um
On Thursday 14 August 2014 03:22 PM, Chen Gang wrote:=0A=
For many individual modules may need check CPU_LITTLE_ENDIAN or=0A= CPU_BIG_ENDIAN, which is an architecture's attribute.=0A= =0A= Or they have to list many architectures which they support, which they=0A= don't support. And still, it is not precise.=0A= =0A= For architecture API, endian is a main architecture's attribute which=0A= may be used by outside, so every architecture need let outside know=0A= about it, explicitly.=0A=
=0A= I don't think that is correct. The modules need to use standard API e.g. sw= ab=0A= which will take care of proper endian handling anyways. Why would a module = do=0A= anything endian specific outside of those APIs.=0A= =0A= And again is this churn just theoretical or do you really have a issue at h= and ! I=0A= would not accept a change for ARC unless you prove that something is broken= (or=0A= atleast potentially broken) !=0A= =0A= -Vineet=0A=