linux-kernel - Re: [PATCH] mach-at91: Support for gms board added.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1291732965.1967.17.camel@homepc>
Date:	Tue, 07 Dec 2010 17:42:45 +0300
From:	Igor Plyatov <plyatov@...il.com>
To:	Ryan Mallon <ryan@...ewatersys.com>
Cc:	linux-arm-kernel@...ts.infradead.org, linux@...im.org.za,
	linux@....linux.org.uk, nicolas.ferre@...el.com,
	plagnioj@...osoft.com, costa.antonior@...il.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mach-at91: Support for gms board added.

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/