public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>,
	"H. Peter Anvin" <hpa@zytor.com>
Cc: eparis@redhat.com, paulmck@linux.vnet.ibm.com,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	zhenglong.cai@cs2c.com.cn, khilman@linaro.org,
	ak@linux.intel.com, mcgrof@suse.com, fabf@skynet.be,
	"dhowells@redhat.com" <dhowells@redhat.com>,
	pefoley2@pefoley.com, mgorman@suse.de, biederm@xmission.com,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Arnd Bergmann <arnd@arndb.de>, Jean Delvare <jdelvare@suse.de>
Subject: Re: [PATCH] init/Kconfig: Add ENDIAN attributes for all architectures using
Date: Wed, 03 Sep 2014 19:47:09 +0800	[thread overview]
Message-ID: <5406FFBD.8010207@gmail.com> (raw)
In-Reply-To: <54055FF8.3080907@gmail.com>

On 09/02/2014 02:13 PM, Chen Gang wrote:
> On 9/2/14 13:17, Paul Gortmaker wrote:
>>
>> OK, but that was not at _all_ what I thought when looking at this...
>>
>> Instead I saw a well intentioned, but perhaps not fully thought out
>> attempt at fixing a largely irrelevant randconfig/allmodconfig of a
>> 1990's vintage ISDN driver coming from that x86-only era, built against
>> an architecture that will never use or support it (microblaze).
>>
>> In today's world, we'd probably not accept a new ethernet driver or
>> filesystem if it was incapable of handling both BE and LE (exception
>> being SoC ethernet physically bound to one specific CPU, of course.)
>> So the justification given in the commit log for expanding the scope to
>> better deal with the stuff found in ISDN and the like was questionable.
>>
> 

I guess, we are mainly focus on: "Is it worthy enough to add *ENDIAN in
init/Kconfig?"

It seems really few modules need depend on LE or BE (although I am still
not quite sure). If it is true, for me, only for architectures, it is
still worthy enough to let all duplicated *ENDIAN to one place.

If it is still worthy, maybe this patch need be improvement (especially,
for its comments), so please help check when you have time, thanks.


Welcome any other members' ideas, suggestions, or completions.

Thanks.

> After a simple search, for crypto, it may be endian sensitive, and for
> architectures may be endian sensitive, in config time.
> 
>   bash-3.2# find ./ | grep Kconfig | xargs grep depend | grep ENDIAN
>   .//arch/arm/mm/Kconfig:	depends on ARCH_SUPPORTS_BIG_ENDIAN
>   .//arch/arm/mm/Kconfig:	depends on CPU_BIG_ENDIAN
>   .//arch/arm/mm/Kconfig:	depends on CPU_BIG_ENDIAN
>   .//arch/arm64/Kconfig:	depends on OF && !CPU_BIG_ENDIAN
>   .//arch/mips/Kconfig:	depends on SYS_SUPPORTS_BIG_ENDIAN
>   .//arch/mips/Kconfig:	depends on SYS_SUPPORTS_LITTLE_ENDIAN
>   .//arch/mips/Kconfig:	depends on SGI_IP22 || SGI_IP28 || (SNI_RM && CPU_LITTLE_ENDIAN)
>   .//arch/powerpc/platforms/Kconfig.cputype:	depends on !CPU_LITTLE_ENDIAN
>   .//arch/powerpc/platforms/Kconfig.cputype:	depends on PPC_BOOK3S_64 && !CPU_LITTLE_ENDIAN
>   .//arch/powerpc/platforms/Kconfig.cputype:	depends on PPC_BOOK3S_64 && !CPU_LITTLE_ENDIAN
>   .//arch/powerpc/platforms/Kconfig.cputype:	depends on PPC_BOOK3S_64 && !CPU_LITTLE_ENDIAN
>   .//arch/powerpc/platforms/Kconfig.cputype:	depends on PPC_BOOK3S_64 && !CPU_LITTLE_ENDIAN
>   .//arch/powerpc/platforms/Kconfig.cputype:	depends on CPU_LITTLE_ENDIAN
>   [...]
>   .//crypto/Kconfig:	depends on ARM && KERNEL_MODE_NEON && !CPU_BIG_ENDIAN
>   .//crypto/Kconfig:	depends on ARM && KERNEL_MODE_NEON && !CPU_BIG_ENDIAN
>   .//drivers/crypto/Kconfig:	depends on PPC64 && IBMVIO && !CPU_LITTLE_ENDIAN
>   [...]
> 
> It is a simple search, so I am not sure whether have other modules also
> need LE or BE.
> 

Thanks.
-- 
Chen Gang

Open, share, and attitude like air, water, and life which God blessed

  reply	other threads:[~2014-09-03 11:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-01 15:46 [PATCH] init/Kconfig: Add ENDIAN attributes for all architectures using Chen Gang
2014-09-01 16:08 ` Paul Gortmaker
2014-09-01 17:01   ` H. Peter Anvin
2014-09-02  1:44     ` Chen Gang
2014-09-02  5:17     ` Paul Gortmaker
2014-09-02  6:13       ` Chen Gang
2014-09-03 11:47         ` Chen Gang [this message]
2014-09-14  9:08           ` Chen Gang
2014-09-15 13:55             ` Arnd Bergmann
2014-09-15 22:41               ` Chen Gang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5406FFBD.8010207@gmail.com \
    --to=gang.chen.5i5j@gmail.com \
    --cc=ak@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=biederm@xmission.com \
    --cc=dhowells@redhat.com \
    --cc=eparis@redhat.com \
    --cc=fabf@skynet.be \
    --cc=geert@linux-m68k.org \
    --cc=hpa@zytor.com \
    --cc=jdelvare@suse.de \
    --cc=khilman@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@suse.com \
    --cc=mgorman@suse.de \
    --cc=paul.gortmaker@windriver.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=pefoley2@pefoley.com \
    --cc=zhenglong.cai@cs2c.com.cn \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox