linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm64: defconfig: enable EEPROM_AT25 config option
Date: Wed, 19 Oct 2016 09:50:31 -0700	[thread overview]
Message-ID: <CAOesGMgoWUG+=61OzxdCCX5oujHC4XOJ-MFGfEyRkrJGq_4fAg@mail.gmail.com> (raw)
In-Reply-To: <5740014.mZjAIri61F@wuerfel>

On Wed, Oct 19, 2016 at 1:04 AM, Arnd Bergmann <arnd@arndb.de> 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

      reply	other threads:[~2016-10-19 16:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-12 18:51 [PATCH v2] arm64: defconfig: enable EEPROM_AT25 config option Scott Branden
2016-10-17 21:58 ` Olof Johansson
2016-10-17 23:24   ` Scott Branden
2016-10-18  0:04     ` Olof Johansson
2016-10-18 20:38       ` Scott Branden
2016-10-18 20:48         ` Olof Johansson
2016-10-18 22:23           ` Scott Branden
2016-10-19  8:04             ` Arnd Bergmann
2016-10-19 16:50               ` Olof Johansson [this message]

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='CAOesGMgoWUG+=61OzxdCCX5oujHC4XOJ-MFGfEyRkrJGq_4fAg@mail.gmail.com' \
    --to=olof@lixom.net \
    --cc=linux-arm-kernel@lists.infradead.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).