From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Naveen N Rao <naveen@kernel.org>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [PATCH v2 1/1] powerpc/8xx: Drop legacy-of-mm-gpiochip.h header
Date: Mon, 24 Nov 2025 17:10:44 +0200 [thread overview]
Message-ID: <aSR1dBucp88ucBvN@smile.fi.intel.com> (raw)
In-Reply-To: <aKXXTcqpi-6TjWrU@smile.fi.intel.com>
On Wed, Aug 20, 2025 at 05:10:21PM +0300, Andy Shevchenko wrote:
> On Thu, Aug 14, 2025 at 10:33:52AM +0200, Christophe Leroy wrote:
> > Le 18/11/2024 à 13:31, Andy Shevchenko a écrit :
> > > Remove legacy-of-mm-gpiochip.h header file. The above mentioned
> > > file provides an OF API that's deprecated. There is no agnostic
> > > alternatives to it and we have to open code the logic which was
> > > hidden behind of_mm_gpiochip_add_data(). Note, most of the GPIO
> > > drivers are using their own labeling schemas and resource retrieval
> > > that only a few may gain of the code deduplication, so whenever
> > > alternative is appear we can move drivers again to use that one.
> > >
> > > As a side effect this change fixes a potential memory leak on
> > > an error path, if of_mm_gpiochip_add_data() fails.
> >
> > Is there a reason for having done this change in cpm1_gpiochip_add16() and
> > cpm1_gpiochip_add32() [arch/powerpc/platform/8xx/cpm1.c] and not in
> > cpm2_gpiochip_add32() [arch/powerpc/sysdev/cpm_common.c] while all three
> > functions are called from cpm_gpio_probe() [arch/powerpc/sysdev/cpm_gpio.c]
> > ?
>
> No specific reason, just lack of time to have got all of the cases.
I have noticed that you cleaned all them up, I appreciate the work, thanks!
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2025-11-24 15:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 12:31 [PATCH v2 1/1] powerpc/8xx: Drop legacy-of-mm-gpiochip.h header Andy Shevchenko
2024-11-18 14:10 ` Christophe Leroy
2024-12-12 16:24 ` Andy Shevchenko
2024-12-13 6:28 ` Christophe Leroy
2024-12-13 17:07 ` Andy Shevchenko
2024-12-13 18:01 ` Christophe Leroy
2024-12-14 22:18 ` Andy Shevchenko
2024-12-16 2:42 ` Madhavan Srinivasan
2025-01-01 9:08 ` Madhavan Srinivasan
2025-08-14 8:33 ` Christophe Leroy
2025-08-20 14:10 ` Andy Shevchenko
2025-11-24 15:10 ` Andy Shevchenko [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=aSR1dBucp88ucBvN@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.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;
as well as URLs for NNTP newsgroup(s).