From: David Miller <davem@davemloft.net>
To: arnd@arndb.de
Cc: babu.moger@oracle.com, mpe@ellerman.id.au, geert@linux-m68k.org,
peterz@infradead.org, mingo@redhat.com,
sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, devicetree@vger.kernel.org,
linux-serial@vger.kernel.org
Subject: Re: CPU_BIG_ENDIAN in generic code
Date: Thu, 08 Jun 2017 10:02:22 -0400 (EDT) [thread overview]
Message-ID: <20170608.100222.1573468093040905016.davem@davemloft.net> (raw)
In-Reply-To: <CAK8P3a1WfU9V1k2r=TfJSVRTymuD8n2hkJDr6u1KcmC_scAZMA@mail.gmail.com>
From: Arnd Bergmann <arnd@arndb.de>
Date: Thu, 8 Jun 2017 10:01:59 +0200
> I would also suggest adding a sanity check like
Hmm, but this will kill the build for non-fixed endian architectures
won't it?
next prev parent reply other threads:[~2017-06-08 14:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 9:59 CPU_BIG_ENDIAN in generic code (was: Re: [PATCH v3 3/7] arch/sparc: Define config parameter CPU_BIG_ENDIAN) Geert Uytterhoeven
2017-05-24 10:18 ` Arnd Bergmann
2017-05-24 14:45 ` Babu Moger
[not found] ` <8ec12d9b-30da-6088-e340-93cc92245ed4-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2017-05-24 15:09 ` Arnd Bergmann
2017-05-24 17:03 ` Babu Moger
[not found] ` <CAK8P3a1XZGQk3b3q+JFJ+mLgw_upUdAtTM1VBjHZq5f2m-YdUg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-25 14:51 ` Babu Moger
2017-05-25 20:09 ` Arnd Bergmann
2017-05-25 20:22 ` Babu Moger
2017-05-25 22:27 ` Max Filippov
2017-05-25 22:41 ` Babu Moger
[not found] ` <116e7ba5-cb5e-8e96-ea74-bf91b4818d69-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2017-05-25 22:52 ` Max Filippov
2017-05-25 22:43 ` Max Filippov
2017-05-29 12:54 ` Arnd Bergmann
[not found] ` <CAMuHMdVjh+1TR19mUUQYHSazHnBHa4uxn7KyHUO+jAh7WDxy5Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-29 12:07 ` Michael Ellerman
2017-05-29 12:15 ` Geert Uytterhoeven
2017-05-30 2:56 ` Michael Ellerman
2017-06-07 23:07 ` Babu Moger
2017-06-08 8:01 ` Arnd Bergmann
2017-06-08 14:02 ` David Miller [this message]
2017-06-08 14:36 ` CPU_BIG_ENDIAN in generic code Arnd Bergmann
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=20170608.100222.1573468093040905016.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=arnd@arndb.de \
--cc=babu.moger@oracle.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=peterz@infradead.org \
--cc=sparclinux@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 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).