From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, URIBL_BLOCKED,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 87DA1C169C4 for ; Thu, 31 Jan 2019 13:24:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 55F56218EA for ; Thu, 31 Jan 2019 13:24:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1548941055; bh=X3P45galx7AD7/UUFgtCWxAZluM6h2YXUaXYGg9+u4c=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=AJQRzKFktInoFyMTnphINjZc/F1FitzafWvRvX4m801Yqlu2u2zO5OO4QE66VIe1G yLJDmEtLeOzcfQytKu9yJ6yDaiD+8TfFwmTWexKBtql1KSVpqqx6bLBAnEhwC9IA7e j1hm3LFPf4RNpi201cGl+BCBG+bHK9A1ZPHKYM5g= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387443AbfAaNYN (ORCPT ); Thu, 31 Jan 2019 08:24:13 -0500 Received: from mail.kernel.org ([198.145.29.99]:33046 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726153AbfAaNYN (ORCPT ); Thu, 31 Jan 2019 08:24:13 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 865102085B; Thu, 31 Jan 2019 13:24:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1548941052; bh=X3P45galx7AD7/UUFgtCWxAZluM6h2YXUaXYGg9+u4c=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=B5uPT+TF8exv6xRKvDO+h08jkJ2ey2R/PrXkIQUqgA2bmWZ10Y+MsLIgiRbrlxx3Q 2AuP47mDMs/mpFUbjr4HCG8o6SytzGA2BFBF4wP/Cvjh6rdzWsrL/teJB3ML7LrO1d Pf4d6rtTrdOwzAqedCr65ziu33PeKF8C3c86JKpg= Date: Thu, 31 Jan 2019 14:24:09 +0100 From: Greg Kroah-Hartman To: "Rafael J. Wysocki" Cc: LKML , Linux PM , Ulf Hansson , Daniel Vetter , Lukas Wunner , Andrzej Hajda , Russell King - ARM Linux , Lucas Stach , Linus Walleij , Thierry Reding , Laurent Pinchart Subject: Re: [PATCH 0/6] driver core: Fix some issues related to device links Message-ID: <20190131132409.GA16084@kroah.com> References: <2493187.oiOpCWJBV7@aspire.rjw.lan> <20190131132247.GA6837@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190131132247.GA6837@kroah.com> User-Agent: Mutt/1.11.2 (2019-01-07) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 31, 2019 at 02:22:47PM +0100, Greg Kroah-Hartman wrote: > On Thu, Jan 31, 2019 at 11:09:51AM +0100, Rafael J. Wysocki wrote: > > On Thu, Jan 24, 2019 at 12:25 PM Rafael J. Wysocki wrote: > > > > > > Hi Greg at al, > > > > > > Recently I have been looking at the device links code because of the > > > recent discussion on possibly using them in the DRM subsystem (see for > > > example https://marc.info/?l=linux-pm&m=154832771905309&w=2) and I have > > > found a few issues in that code which should be addressed by this patch > > > series. Please refer to the patch changelogs for details. > > > > > > None of the problems addressed here should be manifesting themselves in > > > mainline kernel today, but if there are more device links users in the > > > future, they most likely will be encountered sooner or later. Also they > > > need to be fixed for the DRM use case to be supported IMO. > > > > > > This series does not fix all issues in device links that have become > > > apparent (generally speaking, the idea of returning an existing link > > > in case there is one already for the given consumer-supplier pair > > > doesn't play well with stateful links and their flags), so there will > > > be a follow-up series of patches to clean that up. Still, I don't see > > > a reason to sit on these fixes while working on the other patches, so > > > here they go. > > > > Any concerns regarding this lot? > > > > [Please note that patch 5 in the series was replaced with the v2 at > > https://patchwork.kernel.org/patch/10781205/] > > > > If not, and if you don't mind, I would like to queue it up next week, > > possibly along with the follow-up material posted on Monday > > (https://lore.kernel.org/lkml/2405639.4es7pRLqn0@aspire.rjw.lan/) if > > that is not problematic, so it gets some linux-next coverage before > > the next merge window. > > Can I queue it up in my tree, given that I have a number of other driver > core patches in there, and I don't know how the merge issues will be if > we start to diverge. > > Or do you need this for some other work? To make this clearer, I have no objection to take this through my tree now, along with your second set of patches. Is that ok? thanks, greg k-h