From: Johan Hovold <johan@kernel.org>
To: linfordWu <linfordwu@163.com>
Cc: elder@kernel.org, gregkh@linuxfoundation.org,
greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: greybus: fix loopback Kconfig help
Date: Tue, 27 Oct 2026 15:33:18 +0100 [thread overview]
Message-ID: <auC2LiV6564Z1zFg@hovoldconsulting.com> (raw)
In-Reply-To: <20261027142258.1720002-1-linfordwu@163.com>
On Tue, Oct 27, 2026 at 10:22:58PM +0800, linfordWu wrote:
> The loopback driver help text describes the debug log class and names
> gb-log.ko. Update it to describe the loopback class and the actual
> module name, gb-loopback.ko.
How was this issue found and fixed? Did you use an LLM?
This went unnoticed for 10+ years, but a fix for this was posted just
the other week:
https://lore.kernel.org/all/20261018172711.8013-1-sowmyatorra@gmail.com/
Johan
next prev parent reply other threads:[~2026-10-27 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 14:22 [PATCH] staging: greybus: fix loopback Kconfig help linfordWu
2026-10-27 14:33 ` Johan Hovold [this message]
2026-10-29 14:06 ` linfordWu
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=auC2LiV6564Z1zFg@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=linfordwu@163.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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