Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753368AbbKZUAN (ORCPT ); Thu, 26 Nov 2015 15:00:13 -0500 Received: from mail-gw1-out.broadcom.com ([216.31.210.62]:16068 "EHLO mail-gw1-out.broadcom.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751457AbbKZUAK (ORCPT ); Thu, 26 Nov 2015 15:00:10 -0500 X-IronPort-AV: E=Sophos;i="5.20,348,1444719600"; d="scan'208";a="81752920" From: Scott Branden To: "Yann E. MORIN" CC: , , , Scott Branden Subject: [PATCH 0/1] kconfig: add CPU endian selection beconfig and leconfig Date: Thu, 26 Nov 2015 11:59:54 -0800 Message-ID: <1448567995-8784-1-git-send-email-sbranden@broadcom.com> X-Mailer: git-send-email 2.5.0 MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1234 Lines: 37 The proposed patch allows a defconfig to be changed to big or little endian by adding "make beconfig" and "make leconfig" functionality. This follows on from a discussion with existing arm64 builds and lack of ability to build for a big endian defconfig as such defconfig is not in the upstream kernel. Discussion started on the arm mailing list: http://www.spinics.net/lists/arm-kernel/msg462636.html The same problem applies to various architecture families so it makes sense to apply at a higher level as proposed. This patchset is based on v4.4-rc1 and is available from github: repo: https://github.com/Broadcom/arm64-linux.git branch: kconfig-endian-v1 Scott Branden (1): kconfig: add CPU endian selection beconfig and leconfig kernel/configs/be.config | 1 + kernel/configs/le.config | 1 + scripts/kconfig/Makefile | 10 ++++++++++ 3 files changed, 12 insertions(+) create mode 100644 kernel/configs/be.config create mode 100644 kernel/configs/le.config -- 2.5.0 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/