From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-174.mta0.migadu.com (out-174.mta0.migadu.com [91.218.175.174]) (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 C07F6125A9 for ; Fri, 19 Dec 2025 21:41:46 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.174 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766180508; cv=none; b=bJskre7768SANFXIf0hN8gLDiy8TxorxfVv7lAliPHXDcJv0apvdzFDplkV8klb2EAYuwd3cLaj8ElI1kNt9SuchYLeQ0lTO6pMHNea8emUFwEZQDR/yF1mKliC1bUpo31QX7fI4oEFJmEdwzW0nPGzRDGTLrOvz5nad+kCGyGw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766180508; c=relaxed/simple; bh=9Lh9Hid4jZkzZrBWZKGJSi0l7rX5EcL7DA9ua8TsVmA=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Message-Id:References:To; b=hRHNLEMXmwyFjPx19FMz7MlJJWQx6UJ2egWJDaENyNRCfXiTz7e6qjukgd2KREh5T4AeOJSd4c8seHkzAHI7pM3EEm7i2YMvtpRZPAGoxNQjgkGQHUAYC8b/bAijMaBr+B7/SfstvogJq1Hen/In6+jeM4xE+whlg4rR/PXdbfE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=AZuso8uo; arc=none smtp.client-ip=91.218.175.174 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="AZuso8uo" Content-Type: text/plain; charset=us-ascii DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1766180488; 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=9Lh9Hid4jZkzZrBWZKGJSi0l7rX5EcL7DA9ua8TsVmA=; b=AZuso8uonEu7UC4gJ+dnpa3In1jy5HMrI/RgrT/PKDqGWUp7IUOkE8H7pqah1AOEROxVBu IHJUdI+hJFrvHFy8aB+DgYuVkU8dUlF5Qp7IhpOh4/KhPAILC/PzoKom5AAJ/6DDRojmJk A12KbsmdlTPqjKFX6WhuPHYKbekC+w8= Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81.1.4\)) Subject: Re: [PATCH] Documentation: kernel-hacking: Remove comma X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Thorsten Blum In-Reply-To: <87pl8akvkv.fsf@trenco.lwn.net> Date: Fri, 19 Dec 2025 22:40:56 +0100 Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Content-Transfer-Encoding: quoted-printable Message-Id: <7BF3E93E-DA92-4FC0-B352-C3766A97B3CD@linux.dev> References: <20251219171827.44015-2-thorsten.blum@linux.dev> <87pl8akvkv.fsf@trenco.lwn.net> To: Jonathan Corbet X-Migadu-Flow: FLOW_OUT On 19. Dec 2025, at 22:31, Jonathan Corbet wrote: > Thorsten Blum writes: >> The comma is wrong, remove it. >>=20 >> Signed-off-by: Thorsten Blum >> --- >> Documentation/kernel-hacking/hacking.rst | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >>=20 >> diff --git a/Documentation/kernel-hacking/hacking.rst = b/Documentation/kernel-hacking/hacking.rst >> index 0042776a9e17..06fcb7c662d3 100644 >> --- a/Documentation/kernel-hacking/hacking.rst >> +++ b/Documentation/kernel-hacking/hacking.rst >> @@ -49,7 +49,7 @@ User Context >>=20 >> User context is when you are coming in from a system call or other = trap: >> like userspace, you can be preempted by more important tasks and by >> -interrupts. You can sleep, by calling :c:func:`schedule()`. >> +interrupts. You can sleep by calling :c:func:`schedule()`. >=20 > That's a fine change, but can I prevail upon you to get rid of the > usless :c:func: annotation while you're playing with that line? So just `schedule()`? :c:func: is used very often in the same file - maybe we should remove them all in a separate patch? I'm fine either way. Thanks, Thorsten