From: Andy Gross <andy.gross@linaro.org>
To: Timur Tabi <timur@codeaurora.org>
Cc: Christopher Covington <cov@codeaurora.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-arm-msm@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, pelcan@codeaurora.org,
okaya@codeaurora.org
Subject: Re: [PATCH] arm64: defconfig: Enable QDF2432 config options
Date: Tue, 23 Aug 2016 15:36:05 -0500 [thread overview]
Message-ID: <20160823203605.GF30923@hector.attlocal.net> (raw)
In-Reply-To: <57768804.6050006@codeaurora.org>
On Fri, Jul 01, 2016 at 10:11:00AM -0500, Timur Tabi wrote:
> Christopher Covington wrote:
> >Due to distribution differences [1][2], I see =y built-in as the default
> >on mobile platforms and =m modular as the default on server platforms.
>
> I don't think we should mix "server" defconfing entries with "mobile"
> defconfig entries. It's a arm64 defconfig, neither server nor mobile. The
> other entries are =y, so these should be =y
>
> No one uses this defconfig as-is for any platform.
>
> >But thinking about it, we could get a poweroff, reset, over-temperature,
> >or other interrupt before we get to the initramfs. So the pin controller
> >driver should be =y built-in.
> >
> >One might make rootfs media =y built-in to make testing easier, but I
> >prefer to put my rootfs on SATA, as SD/MMC is much slower and smaller by
> >comparison.
>
> Let's not overthink things, and just make *everything* =y by default.
Do you guys want me to fix this up so it can hit this window? I can just change
the m to y before I send it off.
Andy
next prev parent reply other threads:[~2016-08-23 20:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 14:12 [PATCH] arm64: defconfig: Enable QDF2432 config options Christopher Covington
2016-07-01 14:14 ` Timur Tabi
2016-07-01 15:06 ` Christopher Covington
2016-07-01 15:11 ` Timur Tabi
2016-08-23 20:36 ` Andy Gross [this message]
2016-08-23 20:36 ` Timur Tabi
2016-07-01 14:27 ` [PATCH v2] " Christopher Covington
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=20160823203605.GF30923@hector.attlocal.net \
--to=andy.gross@linaro.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=cov@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=okaya@codeaurora.org \
--cc=pelcan@codeaurora.org \
--cc=timur@codeaurora.org \
--cc=will.deacon@arm.com \
/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