All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Yury Norov <yury.norov@gmail.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: Wed, 26 Nov 2025 09:59:16 +0200	[thread overview]
Message-ID: <aSazVLj29Ea204ci@smile.fi.intel.com> (raw)
In-Reply-To: <aSTfSkffTnTfR64-@smile.fi.intel.com>

On Tue, Nov 25, 2025 at 12:42:23AM +0200, Andy Shevchenko wrote:
> On Mon, Nov 24, 2025 at 04:17:51PM -0500, Yury Norov wrote:
> > On Mon, Nov 24, 2025 at 09:39:59PM +0100, Andy Shevchenko wrote:
> 
> > > Not fully compile tested, might give some compilation errors

...

> > > -#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.
> 
> Yeah, there are several headers that are too tangled together.
> At least it builds on my configurations on x86_64.
> 
> > Added this for testing in bitmap-for-next.
> 
> Thanks, let's see how it will go. But note that it might fall the builds in
> some cases.

So, we survived already a couple of Linux Next integration builds, I believe
we are quite okay with this change and if anything appears, it can be fixed
in a followups.

Thanks!

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2025-11-26  7:59 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
2025-11-24 22:42   ` Andy Shevchenko
2025-11-26  7:59     ` Andy Shevchenko [this message]
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=aSazVLj29Ea204ci@smile.fi.intel.com \
    --to=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 \
    --cc=yury.norov@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 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.