From: Michael Ellerman <mpe@ellerman.id.au>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
Andi Shyti <andi.shyti@kernel.org>,
Abhinav Jain <jain.abhinav177@gmail.com>
Cc: "javier.carrasco.cruz@gmail.com" <javier.carrasco.cruz@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Julia Lawall <julia.lawall@inria.fr>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"skhan@linuxfoundation.org" <skhan@linuxfoundation.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] i2c: mpc: Removal of of_node_put with __free for auto cleanup
Date: Fri, 19 Apr 2024 17:22:43 +1000 [thread overview]
Message-ID: <87plulakak.fsf@mail.lhotse> (raw)
In-Reply-To: <2ea08951-3613-4ed5-a2b2-dd4887105ac3@alliedtelesis.co.nz>
Chris Packham <Chris.Packham@alliedtelesis.co.nz> writes:
> On 16/04/24 08:54, Andi Shyti wrote:
>> Hi Abhinav,
>>
>>> /* Enable I2C interrupts for mpc5121 */
>>> - node_ctrl = of_find_compatible_node(NULL, NULL,
>>> - "fsl,mpc5121-i2c-ctrl");
>>> + struct device_node *node_ctrl __free(device_node) =
>> How have you tested this?
>
> I'm not sure I know anyone that still has a mpc5121. Maybe someone on
> linuxppc-dev?
Not that I know of.
The driver loads on my T4240, but doesn't hit the right paths to test
this patch.
No objection to it being merged though.
cheers
prev parent reply other threads:[~2024-04-19 7:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240415161220.8347-1-jain.abhinav177@gmail.com>
[not found] ` <vegjt4pcl2x2wmwso6ajbihqc6rpbup5knycnz76jz3zfbfpp4@opxek6apu3w4>
2024-04-16 3:59 ` [PATCH] i2c: mpc: Removal of of_node_put with __free for auto cleanup Chris Packham
2024-04-16 14:07 ` Andi Shyti
2024-04-16 14:09 ` Andi Shyti
2024-04-19 7:22 ` Michael Ellerman [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=87plulakak.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=andi.shyti@kernel.org \
--cc=jain.abhinav177@gmail.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=julia.lawall@inria.fr \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=skhan@linuxfoundation.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).