From: Jean Delvare <jdelvare@suse.de>
To: Nicolai Stange <nicstange@gmail.com>
Cc: David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
isdn@linux-pingi.de, Chen Gang <gang.chen.5i5j@gmail.com>,
Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH] isdn: disable HiSax NetJet driver on microblaze arch
Date: Mon, 22 Jun 2015 13:27:33 +0200 [thread overview]
Message-ID: <1434972453.4568.8.camel@chaos.site> (raw)
In-Reply-To: <87y4jdc58w.fsf@gmail.com>
Le Sunday 21 June 2015 à 19:59 +0200, Nicolai Stange a écrit :
> David Miller <davem@davemloft.net> writes:
> >> Note that endianess on microblaze is not determined through Kconfig,
> >> but by means of a compiler provided CPP macro, namely __MICROBLAZEEL__.
> >> However, gcc defaults to big endianess on that platform.
> > Applied, but we're long overdue for an across-the-board-available
> > endianness Kconfig option that can flat out be used in these situations.
> > The current way this is handled is at best, a mess.
I fully agree.
> Thanks!
>
> Regarding the general Kconfig endianess symbol, I will do another patch
> based on the information of
> git grep '_endian\.h' -- arch/
> and supply every arch with either of CONFIG_CPU_{LITTLE,BIG}_ENDIAN if
> lacking.
Note that Chen Gang (Cc'd) attempted the same almost a year ago:
http://patchwork.linux-mips.org/patch/7540/
then:
http://marc.info/?t=140958656400002&r=1&w=2
The idea was great IMHO but it did not work out, and I can't remember
why.
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2015-06-22 11:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 1:05 [PATCH] isdn: disable HiSax NetJet driver on microblaze arch Nicolai Stange
2015-06-17 6:53 ` Jean Delvare
2015-06-17 10:58 ` Nicolai Stange
2015-06-21 16:54 ` David Miller
2015-06-21 17:59 ` Nicolai Stange
2015-06-22 11:27 ` Jean Delvare [this message]
2015-06-22 12:36 ` Nicolai Stange
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=1434972453.4568.8.camel@chaos.site \
--to=jdelvare@suse.de \
--cc=davem@davemloft.net \
--cc=gang.chen.5i5j@gmail.com \
--cc=isdn@linux-pingi.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicstange@gmail.com \
--cc=ralf@linux-mips.org \
/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;
as well as URLs for NNTP newsgroup(s).