linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	Joe Hattori <joe@pf.is.s.u-tokyo.ac.jp>,
	Konrad Dybcio <konradybcio@gmail.com>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Marijn Suijten <marijn.suijten@somainline.org>,
	linux-kernel@vger.kernel.org,
	Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
	Abel Vesa <abel.vesa@linaro.org>,
	Johan Hovold <johan+linaro@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH v2] spmi: Fix controller->node != parent->node breakage
Date: Wed, 15 Jan 2025 15:16:10 -0800	[thread overview]
Message-ID: <848b4dad4f38dc6545b97f7c5007e514.sboyd@kernel.org> (raw)
In-Reply-To: <91e2bd5b-71fa-402a-82cb-e68d3295804a@gmail.com>

Quoting Konrad Dybcio (2025-01-14 12:37:20)
> On 1/14/25 19:30, Stephen Boyd wrote:
> > 
> > Ok, I see that I was reading the already reverted state of the tree
> > where the 'ctrl->dev.of_node = node' assignment came back. So there's
> > nothing to do besides drop the patch in fixes, which I already did. We
> > can then apply this patch to drop the duplicate assignment as a cleanup
> > and to avoid a refcount bump on the of_node that isn't needed.
> > 
> > ----8<---
> > diff --git a/drivers/spmi/hisi-spmi-controller.c b/drivers/spmi/hisi-spmi-controller.c
> > index 3cafdf22c909..122140b97579 100644
> > --- a/drivers/spmi/hisi-spmi-controller.c
> > +++ b/drivers/spmi/hisi-spmi-controller.c
> > @@ -300,9 +300,6 @@ static int spmi_controller_probe(struct platform_device *pdev)
> >   
> >       spin_lock_init(&spmi_controller->lock);
> >   
> > -     ctrl->dev.parent = pdev->dev.parent;
> > -     ctrl->dev.of_node = of_node_get(pdev->dev.of_node);
> > -
> >       /* Callbacks */
> >       ctrl->read_cmd = spmi_read_cmd;
> >       ctrl->write_cmd = spmi_write_cmd;
> 
> That works for me, thank you
> 

Joe, care to send this patch to replace the one you sent previously?


  reply	other threads:[~2025-01-15 23:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-13 13:02 [PATCH v2] spmi: Fix controller->node != parent->node breakage Konrad Dybcio
2025-01-13 13:52 ` AngeloGioacchino Del Regno
2025-01-13 21:52 ` Stephen Boyd
2025-01-13 22:12   ` Konrad Dybcio
2025-01-14 18:30     ` Stephen Boyd
2025-01-14 20:37       ` Konrad Dybcio
2025-01-15 23:16         ` Stephen Boyd [this message]
2025-01-16  4:54           ` Joe Hattori

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=848b4dad4f38dc6545b97f7c5007e514.sboyd@kernel.org \
    --to=sboyd@kernel.org \
    --cc=abel.vesa@linaro.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=bjorn.andersson@oss.qualcomm.com \
    --cc=joe@pf.is.s.u-tokyo.ac.jp \
    --cc=johan+linaro@kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@gmail.com \
    --cc=konradybcio@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=marijn.suijten@somainline.org \
    --cc=matthias.bgg@gmail.com \
    --cc=mchehab+huawei@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).