Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp3034217imj; Mon, 11 Feb 2019 12:40:04 -0800 (PST) X-Google-Smtp-Source: AHgI3IZHYkv6xEMrngQlYUJeA9f7clQwccyhOm0hj5N75NT3kf7OgbxT75EDqSYt1ssBFtJ0Tq/g X-Received: by 2002:a62:5789:: with SMTP id i9mr95346pfj.75.1549917604474; Mon, 11 Feb 2019 12:40:04 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549917604; cv=none; d=google.com; s=arc-20160816; b=Ge+1Z6yq5IatQGttUEOVIK9IP7IoKoqG0WzYq8xHpU2HbXLGHeZyX3gxYZBsYCoPkm xHraCy/y041/MVDzkk8kDix1Ya8AOVf8xKcmPqsPYikQaoDrh84IXi/Rc4wonZTrwD8n J+iPhUUiTer/S255u80g93wyQ6ny+ot/cg9YBMPCL98wjgo1cpeMcelqR/E8FV9LAR8/ N/lHzptZ+xsK1g7zdzaBiE3Ve2NpYPFMYYlMAn44WyU5bFuozDS4AY+Ygo/NmwH6vF2i cEhh+IBPh8NFW9WLdE/NMF/O3g/m7LskLISua9zpqslbufZ6agpLkfplaxPlvs075ajs d5ow== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :in-reply-to:subject:cc:to:from:message-id:date; bh=UatxRo7gxYX0i31C686wJ9NVhIQMHkLrusQtyXWqigE=; b=Y3ujtgys+YtoxKn0g/CmCHXtY2bXTmKbQUKqkip0OgeB7pgJCFR3LYR9qIRBa5U5hf MNle7Ur2NHWvPdDZxkpKs5nNuP+i8owWRpiyVmx51i1VghllzDiLBnAu+K8/Ez3p317c 19JQSHw+uTBMG8B5YmenejKCDg59pDhZvDJs76j2X4PBFcEl5tJa4lxgPbOsfFGONLLy PhrRjU0xFk+r/jpm4aAm5D8TaLFozEIkW2kYYgFEnNHrOHb5JXJFGHGgaT1qT4i9HOFv wHqEMYxf2bS4E3dvkfcxxSHhZ82pqJ8tv25RpPXKIFw3LM98p/f6DuHAlbB8POxThIKG m8+A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j11si11739569plb.253.2019.02.11.12.39.48; Mon, 11 Feb 2019 12:40:04 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732805AbfBKS5K (ORCPT + 99 others); Mon, 11 Feb 2019 13:57:10 -0500 Received: from mx2.suse.de ([195.135.220.15]:57808 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727197AbfBKS5K (ORCPT ); Mon, 11 Feb 2019 13:57:10 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 98C3CB13C; Mon, 11 Feb 2019 18:57:08 +0000 (UTC) Date: Mon, 11 Feb 2019 19:57:07 +0100 Message-ID: From: Takashi Iwai To: "Sam Ravnborg" Cc: "Daniel Vetter" , "Arnd Bergmann" , "Maxime Ripard" , "Rodrigo Vivi" , "Jani Nikula" , "Joonas Lahtinen" , "Maarten Lankhorst" , "Greg KH" , "discussion and development DRM maintainer tools announcements" , "dri-devel" , "intel-gfx" , "Sean Paul" , , "Linux Kernel Mailing List" Subject: Re: [PULL] topic/component-typed In-Reply-To: <20190211182512.GA28363@ravnborg.org> References: <20190211182512.GA28363@ravnborg.org> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 11 Feb 2019 19:25:12 +0100, Sam Ravnborg wrote: > > Hi Daniel. > > On Mon, Feb 11, 2019 at 06:15:20PM +0100, Daniel Vetter wrote: > > Hi all, > > > > Here's the typed component topic branch. > > > > drm-intel maintainers: Please pull, I need this for the mei hdcp work from Ram. > > > > drm-misc maintainers: Please pull, there's a drm doc patch follow-up > > that I want to stuff into drm-misc-next. > > > > Greg: The drm side missed our feature cutoff, so will only land in 5.2. > > With all the dependencies why not bend the rule a little and get this in now? > It is not like this is a huge patchset. Yeah, that's likely the most straightforward way. BTW, I tried to pull onto sound git tree for-next branch, and it worked without conflicts. So I don't think it needs to be pulled onto mine. thanks, Takashi