From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752126AbdFHOCr (ORCPT <rfc822;w@1wt.eu>);
        Thu, 8 Jun 2017 10:02:47 -0400
Received: from shards.monkeyblade.net ([184.105.139.130]:56260 "EHLO
        shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751449AbdFHOCo (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 8 Jun 2017 10:02:44 -0400
Date: Thu, 08 Jun 2017 10:02:22 -0400 (EDT)
Message-Id: <20170608.100222.1573468093040905016.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
From: David Miller <davem@davemloft.net>
In-Reply-To: <CAK8P3a1WfU9V1k2r=TfJSVRTymuD8n2hkJDr6u1KcmC_scAZMA@mail.gmail.com>
References: <877f0z6oig.fsf@concordia.ellerman.id.au>
        <28d6c874-4653-b15d-39b7-57a032abc9c6@oracle.com>
        <CAK8P3a1WfU9V1k2r=TfJSVRTymuD8n2hkJDr6u1KcmC_scAZMA@mail.gmail.com>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Thu, 08 Jun 2017 06:20:45 -0700 (PDT)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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?