From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Julian Braha <julianbraha@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kconfirm: patch reporting guidelines?
Date: Thu, 7 May 2026 07:10:18 +0200 [thread overview]
Message-ID: <2026050728-construct-tingle-0852@gregkh> (raw)
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
next prev parent reply other threads:[~2026-05-07 5:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 17:08 kconfirm: patch reporting guidelines? Julian Braha
2026-05-07 5:10 ` Greg Kroah-Hartman [this message]
2026-05-07 9:19 ` Julian Braha
2026-05-07 10:06 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026050728-construct-tingle-0852@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=julianbraha@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.