From: Chris Ball <chris@printf.net>
To: Roman Peniaev <r.peniaev@gmail.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Ben Gardiner <bengardiner@nanometrics.ca>,
linux-mmc <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH 0/2] mmc-utils: RPMB support
Date: Tue, 12 Aug 2014 15:04:38 +0100 [thread overview]
Message-ID: <86a9797qix.fsf@void.printf.net> (raw)
In-Reply-To: <CACZ9PQVuJv+pup+f8Yu9TOkupvv11KOsRY0WZg223Cp9=7HfSQ@mail.gmail.com> (Roman Peniaev's message of "Tue, 12 Aug 2014 23:01:22 +0900")
Hi Roman,
On Tue, Aug 12 2014, Roman Peniaev wrote:
> Hello all.
>
> Am I too late to change the second patch?
> Few weeks ago I added support of multiple blocks read
> and forgot to send new one :)
>
> I do not want to send incremental patch.
> Can you change the git history?
If you send a v2, I can turn it into an incremental patch by just
copying the changed files over the existing ones. Does that work?
I prefer not to rewrite history.
- Chris.
--
Chris Ball <http://printf.net/>
next prev parent reply other threads:[~2014-08-12 14:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 12:53 [PATCH 0/2] mmc-utils: RPMB support Roman Pen
2014-07-21 12:53 ` [PATCH 1/2] mmc-utils: RPMB: add HMAC SHA256 support Roman Pen
2014-07-21 12:53 ` [PATCH 2/2] mmc-utils: RPMB: add support for 4 rpmb operations Roman Pen
2014-08-12 14:25 ` [PATCH v2 " Roman Pen
2014-08-12 14:30 ` Roman Peniaev
2014-08-12 13:33 ` [PATCH 0/2] mmc-utils: RPMB support Ulf Hansson
2014-08-12 13:48 ` Chris Ball
2014-08-12 14:01 ` Roman Peniaev
2014-08-12 14:04 ` Chris Ball [this message]
2014-08-12 14:06 ` Roman Peniaev
2014-08-12 14:13 ` Chris Ball
2014-08-12 14:33 ` Roman Peniaev
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=86a9797qix.fsf@void.printf.net \
--to=chris@printf.net \
--cc=bengardiner@nanometrics.ca \
--cc=linux-mmc@vger.kernel.org \
--cc=r.peniaev@gmail.com \
--cc=ulf.hansson@linaro.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;
as well as URLs for NNTP newsgroup(s).