From: Heiko Stuebner <heiko@sntech.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Andy Yan <andy.yan@rock-chips.com>,
arnd@arndb.de, kuninori.morimoto.gx@renesas.com,
catalin.marinas@arm.com, riku.voipio@linaro.org,
will.deacon@arm.com, linux-kernel@vger.kernel.org,
krzk@kernel.org, srinivas.kandagatla@linaro.org,
alim.akhtar@samsung.com, horms+renesas@verge.net.au,
treding@nvidia.com, shawn.lin@rock-chips.com
Subject: Re: [PATCH 1/2] arm64: defconfig: enable I2C and DW MMC controller on rockchip platform
Date: Thu, 17 Nov 2016 16:55:09 +0100 [thread overview]
Message-ID: <1583509.9esYpYNt56@phil> (raw)
In-Reply-To: <1473248790-27101-1-git-send-email-andy.yan@rock-chips.com>
Am Mittwoch, 7. September 2016, 19:46:30 CET schrieb Andy Yan:
> I2C and MMC are very basic modules for a board to bootup, as I2C always
> used to configure PMIC and MMC devices often used to store filesytem.
> So enable them here to let the rockchip based arm64 boards can bootup.
>
> Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
applied to a defconfig64 branch, after moving I2C_RK3X between QUP and TEGRA
RCAR seems to be an exception to the otherwise alphabetically sorted list.
Heiko
prev parent reply other threads:[~2016-11-17 17:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 11:46 [PATCH 1/2] arm64: defconfig: enable I2C and DW MMC controller on rockchip platform Andy Yan
2016-09-07 11:50 ` [PATCH 2/2] arm64: defconfig: enable MFD RK808 and RK808 regulator Andy Yan
2016-11-17 16:03 ` Heiko Stuebner
2016-09-19 10:10 ` [PATCH 1/2] arm64: defconfig: enable I2C and DW MMC controller on rockchip platform Andy Yan
2016-11-03 11:06 ` Andy Yan
2016-11-17 15:55 ` Heiko Stuebner [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=1583509.9esYpYNt56@phil \
--to=heiko@sntech.de \
--cc=alim.akhtar@samsung.com \
--cc=andy.yan@rock-chips.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=horms+renesas@verge.net.au \
--cc=krzk@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riku.voipio@linaro.org \
--cc=shawn.lin@rock-chips.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=treding@nvidia.com \
--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;
as well as URLs for NNTP newsgroup(s).