Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp71849pxf; Wed, 24 Mar 2021 21:27:20 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwSCBxiuLXHpTvymLeBkpwNC7RZIOGO9ctpPKJ3sd8Oftr9p/emrSpTlXKb8pwspeATjgLz X-Received: by 2002:aa7:c9d1:: with SMTP id i17mr6735281edt.46.1616646440484; Wed, 24 Mar 2021 21:27:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1616646440; cv=none; d=google.com; s=arc-20160816; b=PxdOrN6e4T53tCUKhqj8w7ovVq7HThcMZF2VuApg7SQF745eDxKNd/QIM2b2iYLyUB nqsr1Qvin9pxpjAxOKeEB4rLTH410/PTpfJnOBqVsSr4vCGEAGd3CoakVENppzrq1UX9 z4Q2k8v+eaWfrN+qWuFB/uo9QtCYt26845ZOzhKdw/9wPRQ2OvHTab3Hy/nURRMaa0i1 ZOC1aIjT9HQB1SD38KMKtht0e/DnTcoES4rgAN48RsqZeqY2EQm6HxEFvdp8qnxLOQyS fApDQZ5FF4Uk98rfiCQpQOyk/IxYDCrC3JsU+brpR25ewXIYd7W32UFTu91Z4RPXFZij dyiQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=/u+4i8WYF2c9ZDk59mboHoPw3gCeJqiy4ub9J1NWaIM=; b=IwtBG2A/Ag3fPee0pe1rcnrHmzYMOYWLF9+WqD90jr6ZysLOWuU4p0lMvhnH+Ly17z wab6lzqTUuwXWP4WVjEnoU9ioWscXWLl3JrSl4B0hfo5Zi+v4dQic6amDpTQrVpwotnQ TUPPYXxYzM2Cf4J1CKlK3QydvvQ1wFLGxROy+CouxNxZw+U0yf/aRdtq73pqhXvZMJJe jTIhhGhoafruMMPx3Zi5KmZNl/Yhs7K8xdbZ2b3pz5SkiDspKw8UnqaXdXiIjKZ+AAJu c24WiviAjFCqi8iKJAKIeDPiSqWe+3TbB8euqaJl4RBRcHxEg+TXbDM2T6q7YN35dJV+ dEpw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=HTlTOhHu; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id x27si3361697edi.240.2021.03.24.21.26.57; Wed, 24 Mar 2021 21:27:20 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=HTlTOhHu; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229508AbhCYE0C (ORCPT + 99 others); Thu, 25 Mar 2021 00:26:02 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33284 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229448AbhCYEZk (ORCPT ); Thu, 25 Mar 2021 00:25:40 -0400 Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6AD40C06174A for ; Wed, 24 Mar 2021 21:25:40 -0700 (PDT) Received: by mail-pg1-x532.google.com with SMTP id 32so559057pgm.1 for ; Wed, 24 Mar 2021 21:25:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=/u+4i8WYF2c9ZDk59mboHoPw3gCeJqiy4ub9J1NWaIM=; b=HTlTOhHuU7HjQBzgmqwLdtDrpQBdQvzt8BYq6m+XnP22XJY4SqLD8OHTwDwApXMgve ADnv4V5CqBgIpHR+awfc61/FoB10kDS6FrWxhDukxdy2dl/FeJiJjUK2e9/erMKyAn+U k7Gxflo+Cn2UnDXm7HH+qfIGTol5WKVB2UKvCXaAukWEjJiIpA5dl0T6ZFVYkjXPC5y6 aCRXV47/PHzCCV9EVp9HkqjNd9OYUPz2i2tjTyC4cpDHp774F+v+hYAn9eJnBFih7EV6 6pkdUHNww092Ojj2IC2vAqIt5JZywy+Q6SjN+RgZhIy/Ab0i1EyZgdHvdhaV2KpoHnui BijA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=/u+4i8WYF2c9ZDk59mboHoPw3gCeJqiy4ub9J1NWaIM=; b=s+mj9Jc9VvZhLFcc125rqH3j7mtu+JGEl1wpt8td9lE3su1Fy+zD3YgytysZGCykLc uhfEiWLpZwSsXpFXuGBCcqq/NweLsFHgLOKAtOWd1XB47KDSr61fKGzwGZiWGmOroWeV fWhlHxHA24aFkEHS8P9cVRJ86KgFhALvKC6mAPM6xe+/CufWDz7gkcOQ5Fp7FPR7gt4U BVRW3Xo0gUdR72OKvwjONE5HFi2A/7BjyUstTcUghoTDqMsQwnEFavy0Nd0hYHTQn3Gq FPeh+zwcaTs8AodQzURmN2ehpp+MwhvjwaU5CnAOJzlW20NIv44ZBBNOrxRHxiNq62G7 sjtw== X-Gm-Message-State: AOAM531hS7jY2OPYJr251p1Y71B7vkln2mUnKu7EviUZW2l7y8MpqmV2 ypFy70U8lClX20EC8pR7Sl6T2Q== X-Received: by 2002:a17:902:a715:b029:e7:147e:fe90 with SMTP id w21-20020a170902a715b02900e7147efe90mr2242738plq.66.1616646339598; Wed, 24 Mar 2021 21:25:39 -0700 (PDT) Received: from localhost ([122.172.6.13]) by smtp.gmail.com with ESMTPSA id u2sm3780197pjy.14.2021.03.24.21.25.34 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 24 Mar 2021 21:25:35 -0700 (PDT) Date: Thu, 25 Mar 2021 09:55:30 +0530 From: Viresh Kumar To: Stanimir Varbanov Cc: Stephen Rothwell , Mauro Carvalho Chehab , Bryan O'Donoghue , Dmitry Osipenko , Linux Kernel Mailing List , Linux Next Mailing List , Mauro Carvalho Chehab , Yangtao Li Subject: Re: linux-next: manual merge of the opp tree with the v4l-dvb tree Message-ID: <20210325042530.5clexogqy77v75sm@vireshk-i7> References: <20210323112705.3094525d@canb.auug.org.au> <20225c7e-1151-7865-2bc6-a1e5694c3d65@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20225c7e-1151-7865-2bc6-a1e5694c3d65@linaro.org> User-Agent: NeoMutt/20180716-391-311a52 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 24-03-21, 16:49, Stanimir Varbanov wrote: > Thanks Stephen! > > On 3/23/21 2:27 AM, Stephen Rothwell wrote: > > Hi all, > > > > Today's linux-next merge of the opp tree got a conflict in: > > > > drivers/media/platform/qcom/venus/pm_helpers.c > > > > between commit: > > > > 08b1cf474b7f ("media: venus: core, venc, vdec: Fix probe dependency error") > > > > from the v4l-dvb tree and commit: > > > > 857219ae4043 ("media: venus: Convert to use resource-managed OPP API") > > > > from the opp tree. > > > > I fixed it up (see below) and can carry the fix as necessary. This > > is now fixed as far as linux-next is concerned, but any non trivial > > conflicts should be mentioned to your upstream maintainer when your tree > > is submitted for merging. You may also want to consider cooperating > > with the maintainer of the conflicting tree to minimise any particularly > > complex conflicts. > > > > I don't know what is the best solution here. > > Viresh, Can I take the OPP API changes through media-tree to avoid > conflicts? I already suggested something similar earlier, and I was expecting Thierry to respond to that.. Not sure who should pick those patches. https://lore.kernel.org/lkml/20210318103250.shjyd66pxw2g2nsd@vireshk-i7/ Can you please respond to this series then ? -- viresh