From nobody Mon Jun 8 15:38:29 2026 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 4423528488D; Thu, 28 May 2026 14:22:39 +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=1779978160; cv=none; b=TwLM6bo/GgyaM6XTNsTOiT6Ru1Q4ks7KzFdhsTYoges3TtM70+lhQFZcKhiaS0b6aeLWhf0Z0VgZmuT62O3Ftoh4Uu3UghK5amraxndnwYHPSUTWZNUiRXoTQ+TrlVklRVeKNhe0WfNLIO38EwseqvhNmpnmPeVqA9jqMb1pICM= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779978160; c=relaxed/simple; bh=wHxsbICgGyeFkfrolnxJbOyL/iP53AVNp2VsKPVfkwk=; h=Date:From:To:Subject:Cc:In-Reply-To:References:MIME-Version: Message-ID:Content-Type; b=urYY94Liz9gCxPE/tiymdzsFu9AXd8CpQpAbDZFH010uY9TZXt8i5/F7G8e8Ij8JHRGTcoO+Ddp07RwzLItSic81tz+ye73b4IRtXvLsIPL4l3wWyCXF65E1/7j2zEyPWSiIgjpySgq+Ou/7xmlkBXS5S99vNjWzPm8ZJVjJZpo= 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=N4HZk8lR; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=B+llfvay; 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="N4HZk8lR"; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="B+llfvay" Date: Thu, 28 May 2026 14:22:35 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1779978157; h=from:from:sender:sender:reply-to: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=Tr+TGh0ibjUo98RfAxWASZpub9C+dBEyiC1QZ5BLtfE=; b=N4HZk8lRgqgoqjUOkZUTDJxQbXdnCv8cqzDVZRCdSYl25sW4NyuojRPCA0e7oqesMorpcB O6MOkiGtlxhxwG6Qk/95Bks/jjqH4Qa1Vxl/kyWYG4986G/3GpaqFiGCsNd+9L8Vf2eoB2 P1rW1CXSr6SmpbnJEUPbpThvPmo5uYn5khJwiWVl04/Ffr5pByXnd8ofb5zww0Zfmja06A yWWZa2Zp3Oq4m3ccDP2whZ1dTUivu7pkTUXPeB0heKrUonORottSkHT5ZW0mRZNU8tgb5Z Xxca+vBX7dSSK/ZQiFwj353T3meHHijRRkbY+SMc+EUhWd77azgcUXiCsHrvuw== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1779978157; h=from:from:sender:sender:reply-to: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=Tr+TGh0ibjUo98RfAxWASZpub9C+dBEyiC1QZ5BLtfE=; b=B+llfvayZzTZ/Y6mUL9hcGhqgVaYtLis4OIYhlgWp78LG5USRcugr/KI+j0NlXnbQ9wHIB pwi20/+PpJkdUECA== From: "tip-bot2 for Zhan Xusheng" Sender: tip-bot2@linutronix.de Reply-to: linux-kernel@vger.kernel.org To: linux-tip-commits@vger.kernel.org Subject: [tip: timers/core] timers/migration: Update stale @online doc to @available Cc: Zhan Xusheng , Thomas Gleixner , x86@kernel.org, linux-kernel@vger.kernel.org In-Reply-To: <20260526022106.1302279-1-zhanxusheng@xiaomi.com> References: <20260526022106.1302279-1-zhanxusheng@xiaomi.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Message-ID: <177997815526.1039918.904696475671871251.tip-bot2@tip-bot2> Robot-ID: Robot-Unsubscribe: Contact to get blacklisted from these emails Precedence: bulk Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable The following commit has been merged into the timers/core branch of tip: Commit-ID: 56eb93880c935989c437afee18d6040f356bda21 Gitweb: https://git.kernel.org/tip/56eb93880c935989c437afee18d6040f3= 56bda21 Author: Zhan Xusheng AuthorDate: Tue, 26 May 2026 10:21:06 +08:00 Committer: Thomas Gleixner CommitterDate: Thu, 28 May 2026 16:19:10 +02:00 timers/migration: Update stale @online doc to @available Commit 8312cab5ff47 ("timers/migration: Rename 'online' bit to 'available'") renamed the 'online' field of struct tmigr_cpu to 'available'. The kernel doc comment above the struct still describes the old field name. Update it to reflect the actual field name and use the 'available' wording in the description. Fixes: 8312cab5ff47 ("timers/migration: Rename 'online' bit to 'available'") Signed-off-by: Zhan Xusheng Signed-off-by: Thomas Gleixner Link: https://patch.msgid.link/20260526022106.1302279-1-zhanxusheng@xiaomi.= com --- kernel/time/timer_migration.h | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/kernel/time/timer_migration.h b/kernel/time/timer_migration.h index 291bfb6..ea8db95 100644 --- a/kernel/time/timer_migration.h +++ b/kernel/time/timer_migration.h @@ -94,15 +94,17 @@ struct tmigr_group { /** * struct tmigr_cpu - timer migration per CPU group * @lock: Lock protecting the tmigr_cpu group information - * @online: Indicates whether the CPU is online; In deactivate path - * it is required to know whether the migrator in the top - * level group is to be set offline, while a timer is - * pending. Then another online CPU needs to be notified to - * take over the migrator role. Furthermore the information - * is required in CPU hotplug path as the CPU is able to go - * idle before the timer migration hierarchy hotplug AP is - * reached. During this phase, the CPU has to handle the + * @available: Indicates whether the CPU is available for handling + * global timers. In the deactivate path it is required to + * know whether the migrator in the top level group is to + * be set offline, while a timer is pending. Then another + * available CPU needs to be notified to take over the + * migrator role. Furthermore the information is required + * in the CPU hotplug path as the CPU is able to go idle + * before the timer migration hierarchy hotplug callback is + * reached. During this phase, the CPU has to handle the * global timers on its own and must not act as a migrator. + * @idle: Indicates whether the CPU is idle in the timer migration * hierarchy * @remote: Is set when timers of the CPU are expired remotely