From: Stephen Boyd <sboyd@codeaurora.org>
To: Josh Cartwright <joshc@codeaurora.org>
Cc: David Brown <davidb@codeaurora.org>,
Kumar Gala <galak@codeaurora.org>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] ARM: config: Add qcom_defconfig
Date: Thu, 27 Feb 2014 11:56:14 -0800 [thread overview]
Message-ID: <530F985E.5030503@codeaurora.org> (raw)
In-Reply-To: <20140227154654.GB7308@joshc.qualcomm.com>
On 02/27/14 07:46, Josh Cartwright wrote:
> On Wed, Feb 26, 2014 at 06:16:32PM -0800, Stephen Boyd wrote:
>> Add a defconfig for mach-qcom platforms. Although these platforms
>> are part of the multi-platform kernel, it's useful to have a
>> stripped down version of the defconfig that just selects the
>> Qualcomm based platforms and drivers.
> How minimal are we aiming here? It might be nice to at least get
> DEVTMPFS/DEVTMPFS_MOUNT=y in here, as I think udev barfs without it.
>
Sure that's fine as others are doing the same. I'll send a v1.1.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2014-02-27 19:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 2:16 [PATCH 0/3] Add qcom_defconfig and update msm_defconfig Stephen Boyd
2014-02-27 2:16 ` [PATCH 1/3] ARM: config: Add qcom_defconfig Stephen Boyd
2014-02-27 15:46 ` Josh Cartwright
2014-02-27 19:56 ` Stephen Boyd [this message]
2014-02-27 20:54 ` [PATCH v1.1/3] " Stephen Boyd
2014-02-27 2:16 ` [PATCH 2/3] ARM: msm: Silence readb/writeb warnings due to missing IOMEM() Stephen Boyd
2014-05-27 18:44 ` Olof Johansson
2014-02-27 2:16 ` [PATCH 3/3] ARM: config: Update msm_defconfig Stephen Boyd
2014-02-27 22:14 ` David Brown
2014-02-28 0:22 ` Kumar Gala
2014-05-27 18:05 ` Olof Johansson
2014-05-27 18:40 ` Kumar Gala
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=530F985E.5030503@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=davidb@codeaurora.org \
--cc=galak@codeaurora.org \
--cc=joshc@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).