linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: linux-arm-kernel@lists.infradead.org, arm@kernel.org,
	kernel@collabora.com,
	"Marek Szyprowski" <m.szyprowski@samsung.com>,
	"Yannick Fertré" <yannick.fertre@st.com>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Alexandre Torgue" <alexandre.torgue@st.com>,
	"Biju Das" <biju.das@bp.renesas.com>,
	linux-kernel@vger.kernel.org, "Stefan Agner" <stefan@agner.ch>,
	"Olof Johansson" <olof@lixom.net>,
	"Russell King" <linux@armlinux.org.uk>,
	"Simon Horman" <horms+renesas@verge.net.au>
Subject: Re: [PATCH v2] ARM: multi_v7_defconfig: Enable missing drivers for supported Chromebooks
Date: Tue, 23 Apr 2019 19:54:52 +0200	[thread overview]
Message-ID: <2762752.xXKmUpM1AJ@phil> (raw)
In-Reply-To: <20190307152031.13417-1-enric.balletbo@collabora.com>

Am Donnerstag, 7. März 2019, 16:20:31 CEST schrieb Enric Balletbo i Serra:
> Enable following drivers for merged devices:
> - Batteries with BQ27XXX chips for Minnie boards.
> - Elan eKTH I2C touchscreen for Minnie boards.
> - GPIO charger for all Veyron boards.
> - Rockchip SARADC driver for all rk3288 boards.
> - Rockchip eFUSE driver for all rk3288 boards.
> - TPM security chip for all Veyron boards.
> - ChromeOS EC userspace interface for all chromebooks boards.
> - ChromeOS EC light and proximity sensors for some chromebooks.
> 
> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

applied for 5.2

Thanks
Heiko



      parent reply	other threads:[~2019-04-23 17:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 15:20 [PATCH v2] ARM: multi_v7_defconfig: Enable missing drivers for supported Chromebooks Enric Balletbo i Serra
2019-03-07 18:33 ` Heiko Stübner
2019-04-23 17:54 ` 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=2762752.xXKmUpM1AJ@phil \
    --to=heiko@sntech.de \
    --cc=alexandre.torgue@st.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=biju.das@bp.renesas.com \
    --cc=enric.balletbo@collabora.com \
    --cc=geert+renesas@glider.be \
    --cc=horms+renesas@verge.net.au \
    --cc=kernel@collabora.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=m.szyprowski@samsung.com \
    --cc=olof@lixom.net \
    --cc=stefan@agner.ch \
    --cc=yannick.fertre@st.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).