All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: kexec@lists.infradead.org, Khalid Aziz <khalid@gonehiking.org>
Subject: Re: [PATCH 1/2] kexec-tools: powerpc: Fix function signature of comparefunc()
Date: Wed, 3 Dec 2025 17:24:20 +0000	[thread overview]
Message-ID: <aTByRNlpW0Wh_r2I@horms.kernel.org> (raw)
In-Reply-To: <501429ee083aa7fb07db910e167411fa7707a0f6.camel@physik.fu-berlin.de>

On Sat, Nov 22, 2025 at 12:11:47PM +0100, John Paul Adrian Glaubitz wrote:
> On Wed, 2025-10-22 at 13:44 +0200, John Paul Adrian Glaubitz wrote:
> > Fixes the following build error on 32-bit PowerPC:
> > 
> > kexec/arch/ppc/fs2dt.c: In function 'putnode':
> > kexec/arch/ppc/fs2dt.c:338:51: error: passing argument 4 of 'scandir' from incompatible pointer type [-Wincompatible-pointer-types]
> >   338 |         numlist = scandir(pathname, &namelist, 0, comparefunc);
> >       |                                                   ^~~~~~~~~~~
> >       |                                                   |
> >       |                                                   int (*)(const void *, const void *)
> > 
> > Signed-off-by: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
> > ---
> >  kexec/arch/ppc/fs2dt.c | 3 ++-
> >  1 file changed, 2 insertions(+), 1 deletion(-)
> > 
> > diff --git a/kexec/arch/ppc/fs2dt.c b/kexec/arch/ppc/fs2dt.c
> > index fed499b..d03b995 100644
> > --- a/kexec/arch/ppc/fs2dt.c
> > +++ b/kexec/arch/ppc/fs2dt.c
> > @@ -292,7 +292,8 @@ static void putprops(char *fn, struct dirent **nlist, int numlist)
> >   * Compare function used to sort the device-tree directories
> >   * This function will be passed to scandir.
> >   */
> > -static int comparefunc(const void *dentry1, const void *dentry2)
> > +static int comparefunc(const struct dirent **dentry1,
> > +		       const struct dirent **dentry2)
> >  {
> >  	char *str1 = (*(struct dirent **)dentry1)->d_name;
> >  	char *str2 = (*(struct dirent **)dentry2)->d_name;
> 
> Ping for both patches.

Perhaps this email [1] got lost somehow?

[1] https://lore.kernel.org/kexec/aRM6sOfZdcyB-2j3@horms.kernel.org/

FTR, they have been applied as:

- kexec-tools: powerpc: Fix pointer declarations in read_memory_region_limits()
  https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/commit/?id=6c878e9b8a50
- kexec-tools: powerpc: Fix function signature of comparefunc()
  https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/commit/?id=2786f8eb3e5e


      reply	other threads:[~2025-12-03 17:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-22 11:44 [PATCH 1/2] kexec-tools: powerpc: Fix function signature of comparefunc() John Paul Adrian Glaubitz
2025-10-22 11:44 ` [PATCH 2/2] kexec-tools: powerpc: Fix pointer declarations in read_memory_region_limits() John Paul Adrian Glaubitz
2025-10-22 15:15 ` [Spam] [PATCH 1/2] kexec-tools: powerpc: Fix function signature of comparefunc() Khalid Aziz
2025-10-22 15:20   ` John Paul Adrian Glaubitz
2025-10-22 15:32     ` Khalid Aziz
2025-11-11 13:31 ` Simon Horman
2025-11-22 11:11 ` John Paul Adrian Glaubitz
2025-12-03 17:24   ` Simon Horman [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=aTByRNlpW0Wh_r2I@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=kexec@lists.infradead.org \
    --cc=khalid@gonehiking.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.