From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH] fastboot: explain use of struct fastboot::cmd_exec/flash
Date: Wed, 03 Apr 2024 13:30:16 +0200 [thread overview]
Message-ID: <171214381607.1486839.5233390741337582446.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20240402100006.2484309-1-a.fatoum@pengutronix.de>
On Tue, 02 Apr 2024 12:00:06 +0200, Ahmad Fatoum wrote:
> Commit ed1dded0898f ("usb: gadget: fastboot: Add external command
> execution support") added hooks that allow board code to register its
> own OEM extensions for Fastboot. There are no users of these hooks
> upstream and without digging into the Git history, it's not evident, why
> these hooks are there, especially as the files have been renamed since.
>
> Add a comment to explain what these never-set callbacks are for.
>
> [...]
Applied, thanks!
[1/1] fastboot: explain use of struct fastboot::cmd_exec/flash
https://git.pengutronix.de/cgit/barebox/commit/?id=1eff547a06ed (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2024-04-03 11:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 10:00 Ahmad Fatoum
2024-04-03 11:30 ` Sascha Hauer [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=171214381607.1486839.5233390741337582446.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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