public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yury Norov <yury.norov@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Thomas Huth <thuth@redhat.com>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>
Subject: Re: [rft, PATCH v1 1/1] cpumask: Don't use "proxy" headers
Date: Mon, 24 Nov 2025 16:17:51 -0500	[thread overview]
Message-ID: <aSTLf4Jq5hGbqV4C@yury> (raw)
In-Reply-To: <20251124204128.1273728-1-andriy.shevchenko@linux.intel.com>

On Mon, Nov 24, 2025 at 09:39:59PM +0100, Andy Shevchenko wrote:
> Update header inclusions to follow IWYU (Include What You Use)
> principle.
> 
> Note that kernel.h is discouraged to be included as it's written
> at the top of that file.
> 
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> 
> Not fully compile tested, might give some compilation errors
> 
>  arch/x86/include/asm/cpumask.h |  2 ++
>  include/linux/cpumask.h        | 12 +++++++-----
>  2 files changed, 9 insertions(+), 5 deletions(-)
> 
> diff --git a/arch/x86/include/asm/cpumask.h b/arch/x86/include/asm/cpumask.h
> index 70f6b60ad67b..9df9e9cde670 100644
> --- a/arch/x86/include/asm/cpumask.h
> +++ b/arch/x86/include/asm/cpumask.h
> @@ -2,6 +2,8 @@
>  #ifndef _ASM_X86_CPUMASK_H
>  #define _ASM_X86_CPUMASK_H
>  #ifndef __ASSEMBLER__
> +
> +#include <linux/compiler.h>
>  #include <linux/cpumask.h>
>  
>  extern void setup_cpu_local_masks(void);
> diff --git a/include/linux/cpumask.h b/include/linux/cpumask.h
> index 66694ee8d86e..6abf3d7e9435 100644
> --- a/include/linux/cpumask.h
> +++ b/include/linux/cpumask.h
> @@ -7,14 +7,16 @@
>   * set of CPUs in a system, one bit position per CPU number.  In general,
>   * only nr_cpu_ids (<= NR_CPUS) bits are valid.
>   */
> -#include <linux/cleanup.h>
> -#include <linux/kernel.h>

I recall, removing kernel.h from cpumasks was a troublesome exercise
back then. But it may be my false memory.

Added this for testing in bitmap-for-next.

Thanks,
Yury

> -#include <linux/bitmap.h>
> -#include <linux/cpumask_types.h>
>  #include <linux/atomic.h>
> -#include <linux/bug.h>
> +#include <linux/bitmap.h>
> +#include <linux/cleanup.h>
> +#include <linux/cpumask_types.h>
>  #include <linux/gfp_types.h>
>  #include <linux/numa.h>
> +#include <linux/threads.h>
> +#include <linux/types.h>
> +
> +#include <asm/bug.h>
>  
>  /**
>   * cpumask_pr_args - printf args to output a cpumask
> -- 
> 2.50.1

  reply	other threads:[~2025-11-24 21:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-24 20:39 [rft, PATCH v1 1/1] cpumask: Don't use "proxy" headers Andy Shevchenko
2025-11-24 21:17 ` Yury Norov [this message]
2025-11-24 22:42   ` Andy Shevchenko
2025-11-26  7:59     ` Andy Shevchenko
2025-11-26 15:33       ` Yury Norov

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=aSTLf4Jq5hGbqV4C@yury \
    --to=yury.norov@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=thuth@redhat.com \
    --cc=x86@kernel.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