From: Johan Hovold <johan@kernel.org>
To: Torra Sowmya <sowmyatorra@gmail.com>
Cc: outreachy@lists.linux.dev, 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 text
Date: Mon, 19 Oct 2026 08:43:56 +0200 [thread overview]
Message-ID: <atW8LEl3lo5iS3Gv@hovoldconsulting.com> (raw)
In-Reply-To: <20261018172711.8013-1-sowmyatorra@gmail.com>
On Sun, Oct 18, 2026 at 10:57:11PM +0530, Torra Sowmya wrote:
> The GREYBUS_LOOPBACK help text incorrectly describes the Debug Log
> Class and names gb-log.ko as the module. Correct the description to
> refer to the Loopback Class and name gb-loopback.ko, matching the
> driver and Makefile.
Nice find!
> Signed-off-by: Torra Sowmya <sowmyatorra@gmail.com>
> ---
> drivers/staging/greybus/Kconfig | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/greybus/Kconfig b/drivers/staging/greybus/Kconfig
> index e1d7ffdf4a6f..3ff47550081d 100644
> --- a/drivers/staging/greybus/Kconfig
> +++ b/drivers/staging/greybus/Kconfig
> @@ -75,10 +75,10 @@ config GREYBUS_LOOPBACK
> tristate "Greybus Loopback Class driver"
> help
> Select this option if you have a device that follows the
> - Greybus Debug Log Class specification.
> + Greybus Loopback Class specification.
>
> To compile this code as a module, chose M here: the module
> - will be called gb-log.ko
> + will be called gb-loopback.ko
Reviewed-by: Johan Hovold <johan@kernel.org>
prev parent reply other threads:[~2026-10-19 6:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 17:27 [PATCH] staging: greybus: fix loopback Kconfig help text Torra Sowmya
2026-10-19 6:43 ` Johan Hovold [this message]
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=atW8LEl3lo5iS3Gv@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=sowmyatorra@gmail.com \
/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.