From: Greg KH <gregkh@linuxfoundation.org>
To: Bentley Blacketer <sonionwhat@gmail.com>
Cc: vireshk@kernel.org, johan@kernel.org, elder@kernel.org,
greybus-dev@lists.linaro.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] staging: greybus: bootrom: replace dev_info with dev_dbg for firmware name
Date: Thu, 30 Apr 2026 20:01:57 +0200 [thread overview]
Message-ID: <2026043050-kinetic-unquote-f6b5@gregkh> (raw)
In-Reply-To: <20260430175437.3699-1-sonionwhat@gmail.com>
On Thu, Apr 30, 2026 at 01:54:36PM -0400, Bentley Blacketer wrote:
> The original dev_info call was intentionally temporary, with a FIXME
> comment noting it should be downgraded to dev_dbg once modules with
> valid VID/PID values were common. Project Ara was cancelled in 2016,
> so that time has long passed.
But other systems are now using greybus, and there was at least 2
different phone models that shipped with this code. So are you sure
that there is no user for this anymore?
>
> Remove the FIXME comment and downgrade to dev_dbg as originally intended.
>
> Tested via code inspection only, as Project Ara hardware is no longer
> available.
You can run greybus on a beaglebone device today.
> Signed-off-by: Bentley Blacketer <sonionwhat@gmail.com>
You have an extra ' ' in there still.
> ---
> Changes in v4:
> - Fixed duplicate Signed-off-by
> - Fixed missing tab on snprintf line
> Changes in v3:
> - Fixed author name mismatch
> Changes in v2:
> - Fixed whitespace issues
> - Moved testing note below --- line
>
> drivers/staging/greybus/bootrom.c | 7 +------
> 1 file changed, 1 insertion(+), 6 deletions(-)
>
> diff --git a/drivers/staging/greybus/bootrom.c b/drivers/staging/greybus/bootrom.c
> index 83921d90c..9e0f24d6d 100644
> --- a/drivers/staging/greybus/bootrom.c
> +++ b/drivers/staging/greybus/bootrom.c
> @@ -168,13 +168,8 @@ static int find_firmware(struct gb_bootrom *bootrom, u8 stage)
> intf->ddbl1_manufacturer_id, intf->ddbl1_product_id,
> intf->vendor_id, intf->product_id);
>
> - // FIXME:
> - // Turn to dev_dbg later after everyone has valid bootloaders with good
> - // ids, but leave this as dev_info for now to make it easier to track
> - // down "empty" vid/pid modules.
> - dev_info(&connection->bundle->dev, "Firmware file '%s' requested\n",
> + dev_dbg(&connection->bundle->dev, "Firmware file '%s' requested\n",
> firmware_name);
> -
Why did you drop the blank line too?
thanks,
greg k-h
next prev parent reply other threads:[~2026-04-30 18:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 17:54 [PATCH v4] staging: greybus: bootrom: replace dev_info with dev_dbg for firmware name Bentley Blacketer
2026-04-30 18:01 ` Greg KH [this message]
[not found] ` <CAD3iFGNtqoGUUybvM2kU-hz5vRstukmCY1x9TywF8BairgUypA@mail.gmail.com>
2026-04-30 18:41 ` Greg KH
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=2026043050-kinetic-unquote-f6b5@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=elder@kernel.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=sonionwhat@gmail.com \
--cc=vireshk@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