From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
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>
Subject: Re: [PATCH v1 1/1] powerpc/8xx: Drop legacy-of-mm-gpiochip.h header
Date: Mon, 18 Nov 2024 12:02:44 +0100 [thread overview]
Message-ID: <124ab5ab-3bfd-4ad7-a75d-981da9c03423@csgroup.eu> (raw)
In-Reply-To: <ZzsG9EjzV82Crl2W@smile.fi.intel.com>
Le 18/11/2024 à 10:20, Andy Shevchenko a écrit :
> On Sat, Nov 16, 2024 at 11:44:35AM +0100, Christophe Leroy wrote:
>> Le 15/11/2024 à 14:38, Andy Shevchenko a écrit :
>>> Remove legacy-of-mm-gpiochip.h header file, replace of_* functions
>>> and structs with appropriate alternatives.
>>
>> Looks like you don't really have an alternative to
>> of_mm_gpiochip_add_data(), you are replacing one single line by 11 new ones,
>> and that is done twice (once for cpm1_gpiochip_add16(), once for
>> cpm1_gpiochip_add32()).
>
> True, but that's the issue that we have of_specific API. If someone propose
> the common API for the agnostic approach, it would be nice, but I am not
> the one. And TBH I do not see the advantage of it right now as almost every
> GPIO driver is using its own labeling schema (*). Note, that this patch also
> fixes a memory leak as a side effect.
Can you explain that in the commit message instead of saying you use
appropriate alternatives that do not exist ?
Don't hesitate to mention the memory leak it in the commit message as well.
>
> *) the legacy API is mostly used by PPC code, do you want that of_mm_* thingy
> to be moved to PPC specific code instead of killing it? Would be done this
> way as well.
No no, your change is ok for me, just need an accurate commit message.
>
>>> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>>> ---
>>> arch/powerpc/platforms/8xx/cpm1.c | 119 +++++++++++++++---------------
>>
>> Does not build:
>
> Crap, I most likely built something else and not these files...
> I have carefully build-test this for v2.
Just use mpc885_ads_defconfig
>
> Note to myself: Never ever send the patches on Friday evenings! :-)
>
Christophe
next prev parent reply other threads:[~2024-11-18 11:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 13:38 Andy Shevchenko
2024-11-16 10:44 ` Christophe Leroy
2024-11-18 9:20 ` Andy Shevchenko
2024-11-18 11:02 ` Christophe Leroy [this message]
2024-11-18 12:32 ` Andy Shevchenko
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=124ab5ab-3bfd-4ad7-a75d-981da9c03423@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=andriy.shevchenko@linux.intel.com \
--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
all inboxes | Powered by JetHome®