On Tue, Nov 6, 2018 at 3:31 AM Heiko Stuebner <heiko@xxxxxxxxx> wrote: > Am Donnerstag, 1. November 2018, 13:36:39 CET schrieb Heiko Stuebner: > > Gru-Scarlet is a tablet device using ChomeOS, dual-dsi display > > and Wacom touchscreen with stylus. > > > > There exist two variants in the market using different displays > > that are differentiated via their sku-id. > > The bootloader on them also determines the correct devicetree to > > load via the sku-id. > > > > So add a common scarlet dtsi and two minimal board devicetrees > > for the two display variants. > > > > Signed-off-by: Heiko Stuebner <heiko@xxxxxxxxx> > > looks like I already applied patch1 in time for 4.20 > (and forgot about it), but have now also applied this patch2 > for 4.21 with Rob's review. Thanks, by the way! This worked well for me today, testing 4.20-rc1. Well, except for this silly bit, but that bug has been around (and more or less untested) for several releases: https://lore.kernel.org/patchwork/patch/1008074/ [PATCH] input: cros_ec_keyb: fix button/switch capability reports And this silly one that slipped into this merge window: https://lore.kernel.org/patchwork/patch/1008098/ [PATCH 4.20] ath10k: don't assume 'vif' is non-NULL in flush() *Grumble*: one would think people would test their changes before submitting them, but apparently that's too much to ask.
