All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolai Stange <nicstange@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: nicstange@gmail.com, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, isdn@linux-pingi.de, jdelvare@suse.de
Subject: Re: [PATCH] isdn: disable HiSax NetJet driver on microblaze arch
Date: Sun, 21 Jun 2015 19:59:11 +0200	[thread overview]
Message-ID: <87y4jdc58w.fsf@gmail.com> (raw)
In-Reply-To: <20150621.095400.890337700038231482.davem@davemloft.net> (David Miller's message of "Sun, 21 Jun 2015 09:54:00 -0700 (PDT)")

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.

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at  http://www.tux.org/lkml/

WARNING: multiple messages have this Message-ID (diff)
From: Nicolai Stange <nicstange@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: nicstange@gmail.com, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, isdn@linux-pingi.de, jdelvare@suse.de
Subject: Re: [PATCH] isdn: disable HiSax NetJet driver on microblaze arch
Date: Sun, 21 Jun 2015 19:59:11 +0200	[thread overview]
Message-ID: <87y4jdc58w.fsf@gmail.com> (raw)
In-Reply-To: <20150621.095400.890337700038231482.davem@davemloft.net> (David Miller's message of "Sun, 21 Jun 2015 09:54:00 -0700 (PDT)")

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.

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.

  reply	other threads:[~2015-06-21 17:59 UTC|newest]

Thread overview: 11+ 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 16:54   ` David Miller
2015-06-21 17:59   ` Nicolai Stange [this message]
2015-06-21 17:59     ` Nicolai Stange
2015-06-22 11:27     ` Jean Delvare
2015-06-22 11:27       ` Jean Delvare
2015-06-22 12:36       ` Nicolai Stange
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=87y4jdc58w.fsf@gmail.com \
    --to=nicstange@gmail.com \
    --cc=davem@davemloft.net \
    --cc=isdn@linux-pingi.de \
    --cc=jdelvare@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.