From: Julian Braha <julianbraha@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kconfirm: patch reporting guidelines?
Date: Thu, 7 May 2026 10:19:15 +0100 [thread overview]
Message-ID: <93574fda-f4e1-4937-a699-40e4d1245234@gmail.com> (raw)
In-Reply-To: <2026050728-construct-tingle-0852@gregkh>
On 5/7/26 06:10, Greg Kroah-Hartman wrote:
> What is "kconfirm"?
Sorry again, this is becoming a recurring issue for me with lacking
context...
The introduction of kconfirm to the mailing list is here:
https://lore.kernel.org/all/6ec4df6d-1445-48ca-8f54-1d1a83c4716d@gmail.com/
> 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.
Thank you! I will resubmit the existing patches without Fixes tags, and
continue acknowledging the tool.
- Julian Braha
next prev parent reply other threads:[~2026-05-07 9:19 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
2026-05-07 9:19 ` Julian Braha [this message]
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=93574fda-f4e1-4937-a699-40e4d1245234@gmail.com \
--to=julianbraha@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox