From: adi25charis@gmail.com
To: gregkh@linuxfoundation.org
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] staging: greybus: bootrom: power off module on timeout
Date: Sat, 4 Jul 2026 17:23:01 +0530 [thread overview]
Message-ID: <20260704115301.7113-1-adi25charis@gmail.com> (raw)
In-Reply-To: <2026070430-exclude-improve-f318@gregkh>
On Sat, Jul 04, 2026 at 09:34:47AM +0200, Greg KH wrote:
> Cool, but how was this tested? What hardware needs this?
Fair question. Honestly - I don't have Project Ara hardware, and as
far as I can tell it's not really possible to get any at this point
(the project's been dead for years and I haven't found boards
floating around anywhere).
So this was build-tested only - compiles clean, checkpatch clean -
but I haven't been able to actually trigger the timeout path on real
hardware. I based the fix on the existing gb_svc_intf_eject() usage
elsewhere in the SVC code, so the API usage should be correct, but I
can't vouch for the runtime behavior beyond that.
That said, if this driver is effectively unmaintained at this point
and changes without hardware validation aren't worth taking, I'd
appreciate knowing that as well - happy to defer to your judgment on
whether this is worth pursuing further.
Thanks,
Aditya
next prev parent reply other threads:[~2026-07-04 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-04 7:19 [PATCH] staging: greybus: bootrom: power off module on timeout adi25charis
2026-07-04 7:34 ` Greg KH
2026-07-04 11:53 ` adi25charis [this message]
2026-07-04 14:12 ` kernel test robot
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=20260704115301.7113-1-adi25charis@gmail.com \
--to=adi25charis@gmail.com \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--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