From: Wei Xu <xuwei5@hisilicon.com>
To: Guodong Xu <guodong.xu@linaro.org>, <catalin.marinas@arm.com>,
<will.deacon@arm.com>, <arnd@arndb.de>,
<horms+renesas@verge.net.au>, <treding@nvidia.com>,
<olof@lixom.net>, <kuninori.morimoto.gx@renesas.com>,
<alim.akhtar@samsung.com>, <srinivas.kandagatla@linaro.org>,
<khilman@baylibre.com>, <riku.voipio@linaro.org>,
<john.stultz@linaro.org>
Cc: <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] arm64: defconfig: enable various configs for HiKey
Date: Wed, 24 Aug 2016 16:15:46 +0100 [thread overview]
Message-ID: <57BDBA22.5080600@hisilicon.com> (raw)
In-Reply-To: <1472006527-30620-1-git-send-email-guodong.xu@linaro.org>
Hi Guodong,
On 24/08/2016 03:42, Guodong Xu wrote:
> Enable various configs for HiKey, including:
> 1. HiSilicon Kirin DRM
> 2. ADV7533
> 3. HiSi Powerkey
> 4. Bluetooth
>
Series applied to the hisilicon soc tree.
Thanks!
Best Regards,
Wei
> v2:
> - Removed CMA size 128M change. Leave that in bootloader as suggested by
> Thierry Reding <treding@nvidia.com>
>
> Guodong Xu (3):
> arm64: defconfig: Enable HiSilicon kirin drm, adv7533 for HiKey
> arm64: defconfig: enable CONFIG_INPUT_HISI_POWERKEY for HiKey
> arm64: defconfig: enable bluetooth supports as modules
>
> arch/arm64/configs/defconfig | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
prev parent reply other threads:[~2016-08-24 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 2:42 [PATCH v2 0/3] arm64: defconfig: enable various configs for HiKey Guodong Xu
2016-08-24 2:42 ` [PATCH v2 1/3] arm64: defconfig: Enable HiSilicon kirin drm, adv7533 " Guodong Xu
2016-08-24 2:42 ` [PATCH v2 2/3] arm64: defconfig: enable CONFIG_INPUT_HISI_POWERKEY " Guodong Xu
2016-08-24 2:42 ` [PATCH v2 3/3] arm64: defconfig: enable bluetooth supports as modules Guodong Xu
2016-08-24 15:15 ` Wei Xu [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=57BDBA22.5080600@hisilicon.com \
--to=xuwei5@hisilicon.com \
--cc=alim.akhtar@samsung.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=guodong.xu@linaro.org \
--cc=horms+renesas@verge.net.au \
--cc=john.stultz@linaro.org \
--cc=khilman@baylibre.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=riku.voipio@linaro.org \
--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