Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934589AbdIYKZG (ORCPT ); Mon, 25 Sep 2017 06:25:06 -0400 Received: from mout02.posteo.de ([185.67.36.66]:37464 "EHLO mout02.posteo.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933162AbdIYKZE (ORCPT ); Mon, 25 Sep 2017 06:25:04 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 25 Sep 2017 12:25:01 +0200 From: Martin Kepplinger To: harinath Nampally Cc: Jonathan Cameron , knaack.h@gmx.de, lars@metafoo.de, Peter Meerwald-Stadler , Greg KH , linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org, Alison Schofield Subject: Re: [PATCH 0/3] Refactor event related code In-Reply-To: References: <1506334065-2891-1-git-send-email-harinath922@gmail.com> <5d8c841101a35b47aec56cef1b5a3ff1@posteo.de> Message-ID: <316061dd4135befde8e6fa34d7705108@posteo.de> User-Agent: Posteo Webmail Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 704 Lines: 20 Am 25.09.2017 12:16 schrieb harinath Nampally: >> First, this is at least v2 of this series. Second, it still seems to >> include >> a 4th unrelated patch. > ok I was not sure whether to make it v2 as the change was to only cover > letter > and no code changes. But now I know, will send v3 of this series. > as soon as you don't do an exact resend, increment the version number. When reviewers can ignore all previous versions, they instantly know. And for the case we still want to look at everything, you should include a persistent revision history description below the email's --- dashes. But actually you should have read this and much more in the Documentation directory before sending.