[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZBAmMoV3dOUxBgo+@hovoldconsulting.com>
Date: Tue, 14 Mar 2023 08:45:54 +0100
From: Johan Hovold <johan@...nel.org>
To: Georgi Djakov <djakov@...nel.org>
Cc: Johan Hovold <johan+linaro@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Andy Gross <agross@...nel.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>,
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
Yassine Oudjana <y.oudjana@...tonmail.com>,
Christophe JAILLET <christophe.jaillet@...adoo.fr>,
linux-arm-msm@...r.kernel.org, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] interconnect: qcom: rpm: fix msm8996 interconnect
registration
On Mon, Mar 13, 2023 at 09:57:37PM +0200, Georgi Djakov wrote:
> > Georgi, the offending commit is currently in your icc-next (and local
> > icc-fixes) branch. Perhaps you can fold in the fixup unless you prefer
> > applying it on top.
> >
> > The bogus PM domain lookup is redundant and confusing but should
> > otherwise be benign so the removal could be applied to either branch.
>
> Maybe then I'll just drop this:
> interconnect: qcom: rpm: fix probe PM domain error handling
> and apply this one instead:
> interconnect: qcom: rpm: drop bogus pm domain attach
Sure, that works too. Wasn't sure whether you preferred incremental
fixes on top or not.
I've checked the end result in linux-next against my local branch and
everything looks good.
Thanks for getting that sorted.
Johan
Powered by blists - more mailing lists