From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 6C90C24291E for ; Tue, 28 Oct 2025 17:42:52 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1761673373; cv=none; b=OcwwqlRKfp6nRZnnDRGpQRWocK5D3fYGnGgjpuzyb0m+WAT9Nap6bLPSJLqsF2vcV8UNoXnyD5q2C4IUeAg7F5WjiVMH7YhYhEhgG9ywyKwVbk5fKLVykU321l6B8xDR8HsNNCo0Hvwywc5FiL9zcwpUGRArvjs6rmul0MctITM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1761673373; c=relaxed/simple; bh=9/W+G/NOWtoUPX3G1RgZn0RcBmOw21RSR4+GVFpHTNg=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=W7/pBgWb/cFy/zixK7/V7IDId1OkKdBJUPoj/CvU/Es9DvMIc+hlFvaNGH11aI1erUMJcs6rDgTPRp8Zc31X3j3Z6lQrA0dNcdn11BnoYz0jwiMTsDMJd4GGAw72o5Zwk/l78M7ZwQuV6+fUHInlzErSb1QuBe6U02vkLjCLLfk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=NWeIwKxx; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="NWeIwKxx" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6F6BEC4CEE7; Tue, 28 Oct 2025 17:42:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1761673371; bh=9/W+G/NOWtoUPX3G1RgZn0RcBmOw21RSR4+GVFpHTNg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=NWeIwKxxqc/Z4GPSGOTFFo+9fS+pbKGU7c6S0kXNlpQgmbpdOxZ/FP0PAL1MiLFCa 087eS4jfc5hcZqkCBQ+Y6WXg6Ob8mFGVHSj7mbNUrB1/rmqnemxMYlJKia7HSw+dIH 6gly1tECAKcdS7hzkczLXpEfbEGAKeAQ11Q2x2cjqOhtcTPPcX886FqnCTYF7opUyi IIKL47B/tWYvFezeGjhdtyR9+7bGz5K4VIA8GFX485EknbKQdBsJIO4VDNxfF1AMU/ LnmWBSX2aSX96OfA7buL1plgMd0YmtIaB+2p4NpN/zxHFCuvSvTQBPPWI9dAOJ7cRD fp8D8x0J7WXsQ== Date: Tue, 28 Oct 2025 13:42:50 -0400 From: Sasha Levin To: Miguel Ojeda Cc: Dave Hansen , linux-kernel@vger.kernel.org, Steven Rostedt , Dan Williams , Theodore Ts'o , Jonathan Corbet , Kees Cook , Greg Kroah-Hartman , Shuah Khan Subject: Re: [PATCH] Documentation: Provide guidelines for kernel development tools Message-ID: References: <20251027201204.352890-1-dave.hansen@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=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: On Tue, Oct 28, 2025 at 04:29:14PM +0100, Miguel Ojeda wrote: >On Mon, Oct 27, 2025 at 9:13 PM Dave Hansen wrote: >> + - ChatGPT generated a new function in your patch to sort list entries. >> + - A .c file in the patch was originally generated by Gemini but cleaned >> + up by hand. > >Like Jon, it also crossed my mind using just LLM here or perhaps >mentioning "open" models. On the other hand, it is clear commercial >models are getting used already, e.g. Gemini is in the commit log >already and Claude is in the mailing list. I *think* that this was based on the experience[1] Kees had with LLMs, and my thoughts were that this example would match what a developer were to write if they were asked to document the usage of tooling. And yes, we shouldn't mention proprietary brand names in kernel docs, so I fully agree with Jon and Miguel here. We should however encourage contributors to list the actual tools/LLMs they used, as this could be interesting down the road... [1] https://hachyderm.io/@kees/114907228284590439 -- Thanks, Sasha