From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/4] Rockchip arm64 defconfig updates for 4.18 round 1
Date: Tue, 15 May 2018 23:41:26 +0200 [thread overview]
Message-ID: <5941903.uzDxGiH5hI@diego> (raw)
In-Reply-To: <20180515205354.whll4pj74exaci5h@localhost>
Am Dienstag, 15. Mai 2018, 22:53:54 CEST schrieb Olof Johansson:
> On Tue, May 15, 2018 at 12:40:05PM +0200, Heiko Stuebner wrote:
> > The following changes since commit
60cc43fc888428bb2f18f08997432d426a243338:
> > Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
> >
> > are available in the Git repository at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git
> > tags/v4.18-rockchip-defconfig64-1>
> > for you to fetch changes up to 214f2c319a140f8a0121f362ad8e73ea1576d5ad:
> > arm64: defconfig: enable rockchip efuse (2018-05-09 16:33:09 +0200)
> >
> > ----------------------------------------------------------------
> > Enablement of Rockchip-specific efuse, io-domain and typec drivers
> > as well as general cros-ec, hid, touchscreen bluetooth and wifi-drivers
> > on 64bit arm platforms.
> >
> > ----------------------------------------------------------------
> >
> > Enric Balletbo i Serra (3):
> > arm64: defconfig: Enable typec-phy and extcon-usbc-cros-ec for
> > rk3399
> > arm64: defconfig: Enable Rockchip io-domain driver
> > arm64: defconfig: Enable ChromeOS EC drivers for supported
> > Chromebooks.
> >
> > Ezequiel Garcia (4):
> > arm64: defconfig: Enable HID over I2C drivers
> > arm64: defconfig: Enable Atmel Maxtouch driver
> > arm64: defconfig: Enable Marvell WiFi-Ex PCIe driver
> > arm64: defconfig: Enable bluetooth USB support
> >
> > Heiko Stuebner (1):
> > arm64: defconfig: enable rockchip efuse
>
> Merged. Not sure if it's useful to split defconfig updates quite this
> granular, might make sense to just do slightly more consolidated patches.
>
> Anyway, no harm, just a bit verbose.
ok, I'll check if things can be merged more, the next time :-)
Heiko
next prev parent reply other threads:[~2018-05-15 21:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 10:38 [GIT PULL 1/4] Rockchip driver updates for 4.18 round 1 Heiko Stuebner
2018-05-15 10:38 ` [GIT PULL 2/4] Rockchip dts32 " Heiko Stuebner
2018-05-15 20:52 ` Olof Johansson
2018-05-15 10:39 ` [GIT PULL 3/4] Rockchip dts64 " Heiko Stuebner
2018-05-15 20:52 ` Olof Johansson
2018-05-15 10:40 ` [GIT PULL 4/4] Rockchip arm64 defconfig " Heiko Stuebner
2018-05-15 20:53 ` Olof Johansson
2018-05-15 21:41 ` Heiko Stübner [this message]
2018-05-15 20:51 ` [GIT PULL 1/4] Rockchip driver " Olof Johansson
2018-07-11 14:28 ` [GIT PULL 1/2] Rockchip dts32 updates for 4.19 " Heiko Stuebner
2018-07-11 14:29 ` [GIT PULL 2/2] Rockchip dts64 " Heiko Stuebner
2018-07-14 21:06 ` Olof Johansson
2018-07-14 21:06 ` [GIT PULL 1/2] Rockchip dts32 " Olof Johansson
2018-07-30 22:35 ` [GIT PULL 1/2] Rockchip dts64 updates for 4.19 round 2 Heiko Stuebner
2018-07-30 22:37 ` [GIT PULL 2/2] Rockchip defconfig64 updates for 4.19 Heiko Stuebner
2018-08-01 2:15 ` Olof Johansson
2018-08-01 2:13 ` [GIT PULL 1/2] Rockchip dts64 updates for 4.19 round 2 Olof Johansson
2018-08-06 8:46 ` [GIT PULL] Rockchip dts64 updates for 4.19 round 3 Heiko Stuebner
2018-08-14 11:02 ` Heiko Stuebner
2018-08-24 15:36 ` Olof Johansson
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=5941903.uzDxGiH5hI@diego \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.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).