From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fastboot: allow retrieving fastboot variables from env
Date: Wed, 23 Mar 2016 03:05:47 +0100 [thread overview]
Message-ID: <56F1F9FB.3090305@denx.de> (raw)
In-Reply-To: <20160317174445.3a67ad0f@bbrezillon>
On 03/17/2016 05:44 PM, Boris Brezillon wrote:
> On Thu, 17 Mar 2016 17:21:23 +0100
> Boris Brezillon <boris.brezillon@free-electrons.com> wrote:
>
>> From: Rob Herring <rob.herring@linaro.org>
>>
>> Some boards need to expose device specific variable through fastboot
>> (to adpat the flashing script depending on hardware revision for
>> example).
>>
>> Provide a way to expose custom fastboot variables. Note that all
>> variables meant to be exposed through fastboot should be be prefixed
>> with 'fastboot.', the variable should not exceed 32 bytes (including
>> the prefix and the trailing '\0') and the variable content should
>> fit in the response buffer (60 bytes excluding the 'OKAY' prefix and
>> the trailing '\0').
>>
>> Signed-off-by: Rob Herring <rob.herring@linaro.org>
>> [Boris Brezillon: add a commit message]
>> Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
>>
>> Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
>
> Sorry for the duplicated SoB.
Dropped the double-SoB and applied, thanks!
Best regards,
Marek Vasut
next prev parent reply other threads:[~2016-03-23 2:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 16:21 [U-Boot] [PATCH] fastboot: allow retrieving fastboot variables from env Boris Brezillon
2016-03-17 16:44 ` Boris Brezillon
2016-03-22 22:24 ` Steve Rae
2016-03-22 22:25 ` Steve Rae
2016-03-23 2:05 ` Marek Vasut [this message]
2016-04-02 1:55 ` [U-Boot] " Tom Rini
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=56F1F9FB.3090305@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.de \
/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