From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id BE0B92F60BC for ; Mon, 24 Nov 2025 22:42:23 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.175.65.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764024145; cv=none; b=UgOSRHtZPdHWYVCHxyPBfCGcggcI1xu2++lTMs5i/G5CdhbjBA4mdzPmJvr1m+EOb2uqwL/P78eZZd7w+hvWAPzVbxdGVUT62eztwFr1msUMQ1kVQo8ZW5qA/78lwmT3mZgCOApipj2aMeVXfMfNkjNtzsU/tojaa9st8t6cs9Y= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1764024145; c=relaxed/simple; bh=Tb7ODF+4FucLR8MoZfJFWdkufqN3AJudnWL+F4VPAtg=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=XsCDARRg0EyYFzGE+IHoeI010Ogytn8EEwCktG+uK+Vy4b+38XdlaWVuGycpqCedJ4padYmuoJ+pp9tgWmqI6K8u/R8Ib83YyT2HaB9IL2T7fD8s9pxRAbQm4qduCrA41ugErxbxSkw2mEVpzXWcRLjElvdTrEoG8vW3tKU36ko= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com; spf=pass smtp.mailfrom=linux.intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=fYo8sQaw; arc=none smtp.client-ip=198.175.65.18 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="fYo8sQaw" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1764024144; x=1795560144; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=Tb7ODF+4FucLR8MoZfJFWdkufqN3AJudnWL+F4VPAtg=; b=fYo8sQaw6zTxPXG9cQKqN6kqvMBmRCoYGc4FVi2R9SnO300P19ou3kRu spyK9XAHfevbg0wNALp18x2uMrHfOVFN6PKC339yUQNrWFZo5JpgGk+RC 8jI0XhLYOCo5RiHCh1S9tYTsKoV2p2Q/HbxZHdV4VQjYWFDQPHbwU+DE8 PjIJYyn1ZD8YQKml/2I2PlFKNzzhHaHdGDfdiWI9VljMaIv8KkRyg/egN P88u3v8TNak7IjSi4Mm+R5darngTlUpdeCMuVfVEskvzJuZ7iIpsRJyqf RcH9tTAyTMMbRD/7vIvRxcWQVkPg8fbOReWDdjdC1CpWZFrMtGMx5geuN Q==; X-CSE-ConnectionGUID: CojvKhVdSMuvsUBZEKGDHQ== X-CSE-MsgGUID: I69lcURHSpiGgClHk71nMw== X-IronPort-AV: E=McAfee;i="6800,10657,11623"; a="66066560" X-IronPort-AV: E=Sophos;i="6.20,224,1758610800"; d="scan'208";a="66066560" Received: from fmviesa002.fm.intel.com ([10.60.135.142]) by orvoesa110.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 Nov 2025 14:42:23 -0800 X-CSE-ConnectionGUID: g0kxviZJQTaZQppLJG7gOw== X-CSE-MsgGUID: Lx8BVSWEQ26yDBXncGE16g== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.20,224,1758610800"; d="scan'208";a="215806684" Received: from egrumbac-mobl6.ger.corp.intel.com (HELO localhost) ([10.245.244.5]) by fmviesa002-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 Nov 2025 14:42:21 -0800 Date: Tue, 25 Nov 2025 00:42:18 +0200 From: Andy Shevchenko To: Yury Norov Cc: Thomas Huth , linux-kernel@vger.kernel.org, Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , x86@kernel.org, "H. Peter Anvin" , Rasmus Villemoes Subject: Re: [rft, PATCH v1 1/1] cpumask: Don't use "proxy" headers Message-ID: References: <20251124204128.1273728-1-andriy.shevchenko@linux.intel.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - c/o Alberga Business Park, 6 krs, Bertel Jungin Aukio 5, 02600 Espoo 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 > > -#include > > 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. -- With Best Regards, Andy Shevchenko