linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>,
	Nicola Vetrini <nicola.vetrini@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org,
	regressions@lists.linux.dev, tsbogend@alpha.franken.de,
	anders.roxell@linaro.org, naresh.kamboju@linaro.org
Subject: Re: [PATCH] mips: fix compilation error
Date: Tue, 26 Aug 2025 12:51:56 +0100	[thread overview]
Message-ID: <aK2f3C9bT-cvPR87@casper.infradead.org> (raw)
In-Reply-To: <20250825214245.1838158-1-nicola.vetrini@gmail.com>

On Mon, Aug 25, 2025 at 11:42:45PM +0200, Nicola Vetrini wrote:
> The following build error occurs on a mips build configuration
> (32r2el_defconfig and similar ones)
> ./arch/mips/include/asm/cacheflush.h:42:34: error: passing argument 2 of ‘set_bit’
> from incompatible pointer type [-Werror=incompatible-pointer-types]
>    42 |         set_bit(PG_dcache_dirty, &(folio)->flags)
>       |                                  ^~~~~~~~~~~~~~~
>       |                                  |
>       |                                  memdesc_flags_t *
> 
> This is due to changes introduced by
> commit 30f45bf18d55 ("mm: introduce memdesc_flags_t"), which did not update
> these usage sites.
> 
> Link: https://lore.kernel.org/lkml/CA+G9fYvkpmqGr6wjBNHY=dRp71PLCoi2341JxOudi60yqaeUdg@mail.gmail.com/
> Fixes: 30f45bf18d55 ("mm: introduce memdesc_flags_t")
> Signed-off-by: Nicola Vetrini <nicola.vetrini@gmail.com>
> ---
> First time sending a Linux patch, so I may have gotten some part of
> it wrong.

Well, Naresh was the one who got it wrong BY NOT CCing THE AUTHOR
OF THE PATCH THAT IT WAS BISECTED TO.  Honestly, Naresh, do better.
syzbot manages this, and it's a shell script.

Anyway, this can just be fixed up as the patch is still in mm-new.
Andrew, please apply.

> Bisection was done at the provided link.
> ---
>  arch/mips/include/asm/cacheflush.h | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/arch/mips/include/asm/cacheflush.h b/arch/mips/include/asm/cacheflush.h
> index 1f14132b3fc9..5d283ef89d90 100644
> --- a/arch/mips/include/asm/cacheflush.h
> +++ b/arch/mips/include/asm/cacheflush.h
> @@ -37,11 +37,11 @@
>  #define PG_dcache_dirty			PG_arch_1
>  
>  #define folio_test_dcache_dirty(folio)		\
> -	test_bit(PG_dcache_dirty, &(folio)->flags)
> +	test_bit(PG_dcache_dirty, &(folio)->flags.f)
>  #define folio_set_dcache_dirty(folio)	\
> -	set_bit(PG_dcache_dirty, &(folio)->flags)
> +	set_bit(PG_dcache_dirty, &(folio)->flags.f)
>  #define folio_clear_dcache_dirty(folio)	\
> -	clear_bit(PG_dcache_dirty, &(folio)->flags)
> +	clear_bit(PG_dcache_dirty, &(folio)->flags.f)
>  
>  extern void (*flush_cache_all)(void);
>  extern void (*__flush_cache_all)(void);
> 
> base-commit: 6c68f4c0a147c025ae0b25fab688c7c47964a02f
> -- 
> 2.43.0
> 

      reply	other threads:[~2025-08-26 11:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25 21:42 [PATCH] mips: fix compilation error Nicola Vetrini
2025-08-26 11:51 ` Matthew Wilcox [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=aK2f3C9bT-cvPR87@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=anders.roxell@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=nicola.vetrini@gmail.com \
    --cc=regressions@lists.linux.dev \
    --cc=tsbogend@alpha.franken.de \
    /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).