From: Heiko Stuebner <heiko@sntech.de>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: linux-kernel@vger.kernel.org, kernel@collabora.com,
Arnd Bergmann <arnd@arndb.de>,
Gregory CLEMENT <gregory.clement@bootlin.com>,
Amit Kucheria <amit.kucheria@linaro.org>,
Andy Gross <andy.gross@linaro.org>, Wei Xu <xuwei5@hisilicon.com>,
Will Deacon <will.deacon@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Olof Johansson <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org,
Simon Horman <horms+renesas@verge.net.au>
Subject: Re: [PATCH 1/5] arm64: defconfig: Enable sound support for Samsung Chromebook Plus.
Date: Mon, 23 Jul 2018 12:40:56 +0200 [thread overview]
Message-ID: <1845030.GmhzmUT5kH@phil> (raw)
In-Reply-To: <20180717160610.26501-1-enric.balletbo@collabora.com>
Am Dienstag, 17. Juli 2018, 18:06:06 CEST schrieb Enric Balletbo i Serra:
> Enable the Rockchip sound driver with MAX98357A/RT5514/DA7219 codecs
> needed for the Samsung Chromebook Plus.
>
> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
applied all 5 for 4.19.
As Olof requested less granularity for defconfig changes, I squashed
all of them into one patch enabling Chromebook Plus peripherals.
Thanks
Heiko
prev parent reply other threads:[~2018-07-23 10:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 16:06 [PATCH 1/5] arm64: defconfig: Enable sound support for Samsung Chromebook Plus Enric Balletbo i Serra
2018-07-17 16:06 ` [PATCH 2/5] arm64: defconfig: Enable Infineon TPM security chip Enric Balletbo i Serra
2018-07-17 16:06 ` [PATCH 3/5] arm64: defconfig: Enable vctrl regulators for Gru/Kevin Enric Balletbo i Serra
2018-07-17 16:06 ` [PATCH 4/5] arm64: defconfig: Enable Camera (uvcvideo) support Enric Balletbo i Serra
2018-07-17 16:06 ` [PATCH 5/5] arm64: defconfig: Enable support for SBS battery driver Enric Balletbo i Serra
2018-07-18 14:13 ` [PATCH 1/5] arm64: defconfig: Enable sound support for Samsung Chromebook Plus Gregory CLEMENT
2018-07-23 10:40 ` 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=1845030.GmhzmUT5kH@phil \
--to=heiko@sntech.de \
--cc=amit.kucheria@linaro.org \
--cc=andy.gross@linaro.org \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=enric.balletbo@collabora.com \
--cc=gregory.clement@bootlin.com \
--cc=horms+renesas@verge.net.au \
--cc=kernel@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=will.deacon@arm.com \
--cc=xuwei5@hisilicon.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).