From: Martin Kepplinger <martink@posteo.de>
To: harinath Nampally <harinath922@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
knaack.h@gmx.de, lars@metafoo.de,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Greg KH <gregkh@linuxfoundation.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Alison Schofield <amsfield22@gmail.com>
Subject: Re: [PATCH 0/3] Refactor event related code
Date: Mon, 25 Sep 2017 12:25:01 +0200 [thread overview]
Message-ID: <316061dd4135befde8e6fa34d7705108@posteo.de> (raw)
In-Reply-To: <CAAGUq_o68DAm=nf5P770ZuzpjZCtfxneouWu0mRCXE=0wQmpxA@mail.gmail.com>
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.
prev parent reply other threads:[~2017-09-25 10:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 10:07 Harinath Nampally
2017-09-25 10:07 ` [PATCH 1/3] iio: accel: mma8452: Rename structs holding event configuration registers to more appropriate names Harinath Nampally
2017-09-25 10:07 ` [PATCH 2/3] iio: accel: mma8452: Rename time step look up struct to generic name as the values are same for all the events Harinath Nampally
2017-09-25 10:07 ` [PATCH 3/3] iio: accel: mma8452: Rename read/write event value callbacks to generic function name Harinath Nampally
2017-09-25 10:07 ` [PATCH 4/4] iio: accel: mma8452: Add single pulse/tap event detection feature for fxls8471 Harinath Nampally
2017-09-25 10:11 ` harinath Nampally
2017-09-25 10:11 ` [PATCH 0/3] Refactor event related code Martin Kepplinger
2017-09-25 10:16 ` harinath Nampally
2017-09-25 10:25 ` Martin Kepplinger [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=316061dd4135befde8e6fa34d7705108@posteo.de \
--to=martink@posteo.de \
--cc=amsfield22@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=harinath922@gmail.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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
all inboxes | Powered by JetHome®