From: Jonathan Cameron <jic23@kernel.org>
To: Harinath Nampally <harinath922@gmail.com>, lars@metafoo.de
Cc: Michael.Hennerich@analog.com, knaack.h@gmx.de, pmeerw@pmeerw.net,
gregkh@linuxfoundation.org, linux-iio@vger.kernel.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] coding style warnings fixes
Date: Sun, 14 May 2017 16:23:59 +0100 [thread overview]
Message-ID: <59f9c84c-5336-34c6-dbec-dee28a98997f@kernel.org> (raw)
In-Reply-To: <cover.1494370925.git.harinath922@gmail.com>
On 10/05/17 00:41, Harinath Nampally wrote:
> This revised patchset is for improvement in [PATCH v2 1/3]
> as per the code review comment from Dan Carpenter.
>
> Other two patches [PATCH v2 2/3] and [PATCH v2 3/3] are unchanged,
> so they are same as [PATCH 2/3] and [PATCH 3/3] respectively.
>
> Please find the following related patches:
> [PATCH v2 1/3] staging: iio: meter: Add the comment for mutex definition
> [PATCH v2 2/3] staging: iio: meter: Fix the identations for proper alignments
> [PATCH v2 3/3] staging: iio: meter: Replace symbolic permissions with octal permissions
>
> Harinath Nampally (3):
> staging: iio: meter: Add the comment for mutex definition
> staging: iio: meter: Fix the identations for proper alignments
> staging: iio: meter: Replace symbolic permissions with octal
> permissions
>
> drivers/staging/iio/meter/ade7753.c | 104 ++++++++++++++++++------------------
> 1 file changed, 51 insertions(+), 52 deletions(-)
Please don't post new versions of a patch series as a reply to earlier versions.
It very rapidly leads to deep and unmanageable threads!
Jonathan
>
next prev parent reply other threads:[~2017-05-14 15:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 4:16 [PATCH] staging: iio: meter: This patch fixes warnings found in ade7753.c Harinath Nampally
2017-05-08 4:32 ` Greg KH
2017-05-08 5:35 ` harinath Nampally
2017-05-08 5:38 ` harinath Nampally
2017-05-08 5:42 ` Greg KH
2017-05-09 2:00 ` [PATCH 0/3] coding style warnings fixes Harinath Nampally
2017-05-09 2:00 ` [PATCH 1/3] staging: iio: meter: Add the comment for mutex definition Harinath Nampally
2017-05-09 7:46 ` Dan Carpenter
2017-05-09 23:41 ` [PATCH v2 0/3] coding style warnings fixes Harinath Nampally
2017-05-09 23:41 ` [PATCH v2 1/3] staging: iio: meter: Add the comment for mutex definition Harinath Nampally
2017-05-14 15:24 ` Jonathan Cameron
2017-05-09 23:41 ` [PATCH v2 2/3] staging: iio: meter: Fix the identations for proper alignments Harinath Nampally
2017-05-14 15:26 ` Jonathan Cameron
2017-05-09 23:41 ` [PATCH v2 3/3] staging: iio: meter: Replace symbolic permissions with octal permissions Harinath Nampally
2017-05-14 15:29 ` Jonathan Cameron
2017-05-15 3:10 ` harinath Nampally
2017-05-14 15:23 ` Jonathan Cameron [this message]
2017-05-09 2:00 ` [PATCH 2/3] staging: iio: meter: Fix the identations for proper alignments Harinath Nampally
2017-05-09 2:00 ` [PATCH 3/3] staging: iio: meter: Replace symbolic permissions with octal permissions Harinath Nampally
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=59f9c84c-5336-34c6-dbec-dee28a98997f@kernel.org \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=harinath922@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).