linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alison Schofield <amsfield22@gmail.com>
To: Daniel Baluta <daniel.baluta@intel.com>
Cc: outreachy-kernel@googlegroups.com, jic23@kernel.org,
	linux-iio@vger.kernel.org
Subject: Re: [PATCH] staging: iio: dummy: clean up the define and usage of dummy_scan_elements
Date: Mon, 26 Oct 2015 10:20:46 -0700	[thread overview]
Message-ID: <20151026172045.GA18550@Ubuntu-D830> (raw)
In-Reply-To: <562DE019.3060807@intel.com>

On Mon, Oct 26, 2015 at 10:11:05AM +0200, Daniel Baluta wrote:
> 
> 
> On 10/23/2015 07:54 PM, Alison Schofield wrote:
> >Cleanups related to the usage of dummy_scan_elements in the
> >iio dummy driver:
> >- change enum names to upper case INDEX_*
> >- use the enum for IIO_CHAN_SOFT_TIMESTAMP (rm hard coded value)
> >- comment edited to match changes & follow preferred kernel style
> >
> >Signed-off-by: Alison Schofield <amsfield22@gmail.com>
> >---
> >  drivers/staging/iio/iio_simple_dummy.c        | 22 ++++++++++++----------
> >  drivers/staging/iio/iio_simple_dummy.h        | 20 +++++++++++---------
> >  drivers/staging/iio/iio_simple_dummy_buffer.c |  9 +++++----
> >  3 files changed, 28 insertions(+), 23 deletions(-)
> >
> >diff --git a/drivers/staging/iio/iio_simple_dummy.c b/drivers/staging/iio/iio_simple_dummy.c
> >index 381f90f..5e19068 100644
> >--- a/drivers/staging/iio/iio_simple_dummy.c
> >+++ b/drivers/staging/iio/iio_simple_dummy.c
> >@@ -1,4 +1,4 @@
> >-/**
> >+/*
> This change should be in the 3rd patch.
>
Thanks for the eagle eyes! I see this (and the other comment I edit'd
also.) It leads to another question. 

In these dummy files, there are 27 comment blocks that start with
/** instead of /* .  I touched 2 of them as a passerby, but now
that I'm looking.... should I change them all or is /** that an acceptable
variation.

alison


< snip >

  reply	other threads:[~2015-10-26 17:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23 16:54 [PATCH] staging: iio: dummy: clean up the define and usage of dummy_scan_elements Alison Schofield
2015-10-25  2:33 ` [Outreachy kernel] " Greg KH
2015-10-25 10:54 ` Jonathan Cameron
2015-10-26  3:29   ` Alison Schofield
2015-10-26  7:21     ` Jonathan Cameron
2015-10-26  8:11 ` Daniel Baluta
2015-10-26 17:20   ` Alison Schofield [this message]
2015-10-26 17:32     ` Jonathan Cameron

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=20151026172045.GA18550@Ubuntu-D830 \
    --to=amsfield22@gmail.com \
    --cc=daniel.baluta@intel.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=outreachy-kernel@googlegroups.com \
    /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).