Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756807AbcJSQuf (ORCPT ); Wed, 19 Oct 2016 12:50:35 -0400 Received: from mail-qt0-f196.google.com ([209.85.216.196]:34875 "EHLO mail-qt0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756690AbcJSQud (ORCPT ); Wed, 19 Oct 2016 12:50:33 -0400 MIME-Version: 1.0 X-Originating-IP: [209.133.79.5] In-Reply-To: <5740014.mZjAIri61F@wuerfel> References: <1476298306-9138-1-git-send-email-scott.branden@broadcom.com> <5740014.mZjAIri61F@wuerfel> From: Olof Johansson Date: Wed, 19 Oct 2016 09:50:31 -0700 Message-ID: Subject: Re: [PATCH v2] arm64: defconfig: enable EEPROM_AT25 config option To: Arnd Bergmann Cc: Scott Branden , Catalin Marinas , Will Deacon , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , BCM Kernel Feedback Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1029 Lines: 24 On Wed, Oct 19, 2016 at 1:04 AM, Arnd Bergmann wrote: > On Tuesday, October 18, 2016 3:23:26 PM CEST Scott Branden wrote: >> I have be.config and le.config that allow you to switch the defconfig >> between big and little endian. Does this make sense to upstream to >> arm/configs if you have accepted dram_0x00000000.config? > > Yes, they clearly fall into the same category, let's merge those as well. > >> Would you also accept this to arm64/configs? We actually use >> big and little endian on the same SoC more on arm64 platforms. But, in >> order to boot big endian we need to maintain this outside the kernel >> right now. > > I'm in favor of that, but let's see what the arm64 maintainers think. Single-line fragments aren't really all that valuable, IMHO. Flipping just one option is trivial to do without fragments, or when they're not simple Y/N flips (i.e. like the ram base). Fragments are mostly useful when you need to flip several options together to enable some set of functionality. -Olof