From: plyatov@gmail.com (Igor Plyatov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mach-at91: Support for gms board added.
Date: Tue, 07 Dec 2010 17:42:45 +0300 [thread overview]
Message-ID: <1291732965.1967.17.camel@homepc> (raw)
In-Reply-To: <4CFD4395.6050006@bluewatersys.com>
Dear Ryan,
Thank you for time spent on the patch review.
I will send a new patch with
"[PATCH v2] mach-at91: Support for gms board added" subject.
This patch must be used instead of
"[PATCH] mach-at91: Support for gms board added".
Sorry if I do this incorrectly, but I was unable to find any good
information how to handle patch versioning.
It is unclear which way is required for versioning:
1) send only a next commit as "v2"?
2) send a completely new patch as "v2" which will replace original
patch?
Best regards!
--
Igor Plyatov
prev parent reply other threads:[~2010-12-07 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 19:32 [PATCH] mach-at91: Support for gms board added Igor Plyatov
2010-12-06 20:12 ` Ryan Mallon
2010-12-07 14:42 ` Igor Plyatov [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=1291732965.1967.17.camel@homepc \
--to=plyatov@gmail.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).