From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) (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 41840B67A for ; Wed, 19 Nov 2025 15:56:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=193.142.43.55 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763567812; cv=none; b=hpUHMfopyun64aMArlRhJtciNQfrQbFGF+oqxIMtXVla66LQZq6SAen0BLAzD0B61TqAoZC/Rk5iT7eEgcA6eKVu2lP/FjmoREXwYbCi35Thr96jE1+LbM59fkdXJGoJOVl/FO5jHZ60L6+klFM0AS2V3PDXnj5D5aze8diFvUc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1763567812; c=relaxed/simple; bh=/NrmwU9mjv8ZrdSGZJnK6Ci+XrspejH7WhZ3NEVQ2us=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=OoxSUL9/ApWzebZiMU4ZIBHPZBMNolqDrYklAazBqM3dzpBoEEdxRptr80X7NjroPCP6weNIwGj7MDs4ujbv1WIUXrjpmDrCR8WfMHkdan2acDH3m4Vwwo59HHYbisXAfdf4a4PY2Ia23g54Q6RSgni+CV6AQEn/fQItOsWKp6U= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de; spf=pass smtp.mailfrom=linutronix.de; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=p/xfHi2R; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=EPSFs9l+; arc=none smtp.client-ip=193.142.43.55 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linutronix.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="p/xfHi2R"; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="EPSFs9l+" From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1763567809; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=yMfTlUJI8SdTxYmF3NuRqG9MQmOXQ5hPtWWsOlC21z0=; b=p/xfHi2RsjnPrgKq8+sLU0RVGLR0kUSwy5pjspu9esxRvvJIw4XTS7+auscD7ushIiktAP 18J1m1JDMJlKJtW0MgbKp0HChJwnbwU93F3zl91P25A6cTJ3tCTYJmnz7zACHDY19AioLw aHk7xrkCGADLBycS7TKCirw8S03JQqyrsRnfT1En4zeORqKg6g4ObzQWiTzhiw4acmITP+ aMcBvQWHa5URtci+swRhTCTso3vxrfVId8M+kFy8Idq2Eh6V5M44N4m/EYPtAFfycU0mJP dgQ3isJClEjR3nNwoG0eUiaB5wC4TB9p9m8y9WI8nIBh5kZsvKoOcZLnhttNKw== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1763567809; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=yMfTlUJI8SdTxYmF3NuRqG9MQmOXQ5hPtWWsOlC21z0=; b=EPSFs9l+DqI+llo7oZY4ts1vN0V4twTGf19oOuMZyz/PJKzkeP4mlHAOHL1LiZHjWq9FhG AyqvNDGfe6OWzFCg== To: Gabriele Monaco , linux-kernel@vger.kernel.org, Anna-Maria Behnsen , Frederic Weisbecker , Waiman Long Cc: Gabriele Monaco Subject: Re: [PATCH v15 2/7] timers: Add the available mask in timer migration In-Reply-To: <20251113083324.33490-3-gmonaco@redhat.com> References: <20251113083324.33490-1-gmonaco@redhat.com> <20251113083324.33490-3-gmonaco@redhat.com> Date: Wed, 19 Nov 2025 16:56:48 +0100 Message-ID: <87v7j6kocf.ffs@tglx> 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=utf-8 Content-Transfer-Encoding: quoted-printable On Thu, Nov 13 2025 at 09:33, Gabriele Monaco wrote: Can we please consistently have 'timers/migration:' as prefix like the other existing commits for this series?=20 That allows to write this subject line in a coherent way: timers/migration: Provide and use cpumask for available CPUs or something like that. Why did I waste time for documenting all of this? https://www.kernel.org/doc/html/latest/process/maintainer-tip.html#patch= -subject "=E2=80=98git log path/to/file=E2=80=99 should give you a reasonable hin= t in most cases." Is it really that hard? > Keep track of the CPUs available for timer migration in a cpumask. This > prepares the ground to generalise the concept of unavailable CPUs. > > Reviewed-by: Frederic Weisbecker > Signed-off-by: Gabriele Monaco Aside of the nit above: Reviewed-by: Thomas Gleixner