From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Jimmy Zhang <jimmzhang-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: amartin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [cbootimage PATCH v1] Enhance sign script
Date: Fri, 8 Apr 2016 23:29:23 -0600 [thread overview]
Message-ID: <57089333.2020809@wwwdotorg.org> (raw)
In-Reply-To: <1460167893-10803-1-git-send-email-jimmzhang-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On 04/08/2016 08:11 PM, Jimmy Zhang wrote:
> 1. Add parameter <soc> to sign tegra124 bootimage. Previously it can only sign
> for tegra210
> 2. Automatically generated signed bct. A signed bct is needed during flashing.
>
> Jimmy Zhang (1):
> Add more features
When there is just one patch, or even when there are multiple patches
but there's no need for a series-level explanation, please don't send a
cover letter since it adds no information.
When sending a cover letter, please name it "PATCH 0/n", and name the
patches "m/n". "git format-patch" and "git format-patch --cover-letter"
will do this automatically, so it's less work to do the right thing:-)
prev parent reply other threads:[~2016-04-09 5:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-09 2:11 [cbootimage PATCH v1] Enhance sign script Jimmy Zhang
[not found] ` <1460167893-10803-1-git-send-email-jimmzhang-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-04-09 2:11 ` [cbootimage PATCH v1] Add more features Jimmy Zhang
[not found] ` <1460167893-10803-2-git-send-email-jimmzhang-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-04-11 17:52 ` Stephen Warren
2016-04-09 5:29 ` Stephen Warren [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=57089333.2020809@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=amartin-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=jimmzhang-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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 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.