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 09E3B322C77 for ; Thu, 7 May 2026 05:10:20 +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=1778130621; cv=none; b=lZI12QySa6FNEFUJKqv0tM6/GtgaNoIUNMY77KT2zhwLCdpi5Di8pLVei+Kw5Cl+dimzMg8KHvWDCIUOObJvJafsi5IOp2unj6dP0awxEc1JcKdokWmhQpUgSyMTFUY0TVPjwgQeLCCR3brKeH3m5qcbhJ8B68I7K7PQINkYGbY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778130621; c=relaxed/simple; bh=OsJIrKrFQQuzdW+GpDRHgxA2+MLT4dC/4ex6JLAuc8s=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=KkanfpUBkCURoWcd7O4lGQF7caxi6dA62/OTctoFIr33V/bXQApgjaHxLhltsmBwzixtDnqcD09/qimFFdF9RBk3O7liEmUDA89aFGR38Zp+WKuxZ993kcGrNSkoy+rilui9CsAQ971hoGiF6JmtTC9SCdvr2eGbHYUjYlJjs14= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=XRGOop7X; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="XRGOop7X" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 72598C2BCB8; Thu, 7 May 2026 05:10:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1778130620; bh=OsJIrKrFQQuzdW+GpDRHgxA2+MLT4dC/4ex6JLAuc8s=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=XRGOop7XxLZCjCXQcf4Y+JPtOHGLCUzbtqPQo1q1lI0pVaWLMFapsEVqC5ij8Lw1o dYdV41R/Rv7omtdXTw83DCn64msB7F9snh4zSKyCgJv2zYnwAftcmq2kNua/AAAUTq MJMYWx5+SjaAUjhzQkRfbM5QA6ux3b2LFkD/W/LA= Date: Thu, 7 May 2026 07:10:18 +0200 From: Greg Kroah-Hartman To: Julian Braha Cc: linux-kernel@vger.kernel.org Subject: Re: kconfirm: patch reporting guidelines? Message-ID: <2026050728-construct-tingle-0852@gregkh> References: <3ea75d69-26af-46f9-8d9f-3d6407d51835@gmail.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: <3ea75d69-26af-46f9-8d9f-3d6407d51835@gmail.com> On Wed, May 06, 2026 at 06:08:45PM +0100, Julian Braha wrote: > Hi Greg, > > > *Question 1: should I acknowledge the kconfirm tool in my patches? What is "kconfirm"? > I've received a wide range of feedback as I've been submitting patches > from kconfirm findings. For example, Lorenzo thanked me for > acknowledging the tool when submitting a patch: > https://lore.kernel.org/all/bfdfdb05-77e2-455d-b68d-9da3fd9d1c0d@lucifer.local/ > > and on the other hand, Alexander asked me not to refer to the tool > until it is moved into the tree: > https://lore.kernel.org/all/3ec20142-09d1-436f-a623-21a2440ef7f0-agordeev@linux.ibm.com/ The issue is that you are adding Fixes: tags for something that is not really a fix. And each maintainer has their own opinion, but adding a line saying what tool you are using is a requirement of ours, so this is fine to keep. > *Question 2: do bugs in kconfig deserve a Fixes tag? Probably not. thanks, greg k-h