public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Georgi Djakov <djakov@kernel.org>
Cc: Johan Hovold <johan+linaro@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Andy Gross <agross@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Yassine Oudjana <y.oudjana@protonmail.com>,
	Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] interconnect: qcom: rpm: fix msm8996 interconnect registration
Date: Tue, 14 Mar 2023 08:45:54 +0100	[thread overview]
Message-ID: <ZBAmMoV3dOUxBgo+@hovoldconsulting.com> (raw)
In-Reply-To: <3995e6b4-b222-6152-0292-29ed3704de02@kernel.org>

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

      reply	other threads:[~2023-03-14  7:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13  8:49 [PATCH 0/2] interconnect: qcom: rpm: fix msm8996 interconnect registration Johan Hovold
2023-03-13  8:49 ` [PATCH 1/2] " Johan Hovold
2023-03-13  8:57   ` Konrad Dybcio
2023-03-13  9:11     ` Johan Hovold
2023-03-13  8:49 ` [PATCH 2/2] interconnect: qcom: rpm: drop bogus pm domain attach Johan Hovold
2023-03-13  9:10   ` Konrad Dybcio
2023-03-13 19:58   ` Georgi Djakov
2023-03-14  7:46     ` Johan Hovold
2023-03-13 19:57 ` [PATCH 0/2] interconnect: qcom: rpm: fix msm8996 interconnect registration Georgi Djakov
2023-03-14  7:45   ` Johan Hovold [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZBAmMoV3dOUxBgo+@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=djakov@kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=johan+linaro@kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=y.oudjana@protonmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox