All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Vandre <bvandre@gmail.com>
To: gregkh@linuxfoundation.org, jic23@kernel.org,
	alexandre.belloni@free-electrons.com, linux-iio@vger.kernel.org,
	marex@denx.de
Cc: Brian Vandre <bvandre@gmail.com>, linux-kernel@vger.kernel.org
Subject: [PATCH v2] Staging: iio: adc: Checkpatch.pl warning cleanups
Date: Tue, 21 Oct 2014 17:56:46 -0500	[thread overview]
Message-ID: <cover.1413931615.git.bvandre@gmail.com> (raw)
In-Reply-To: <cover.1413858979.git.bvandre@gmail.com>

This patch-set fixes 2 checkpatch.pl warnings
dealing with lines over 80 characters.

Changes from v1:
-squashed 2 patches into 1 as suggested by Alexandre Belloni


Brian Vandre (1):
  Staging: iio: adc: fix line over 80 characters

 drivers/staging/iio/adc/mxs-lradc.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

-- 
1.9.1

  parent reply	other threads:[~2014-10-21 22:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21  2:48 [PATCH 0/2] Staging: iio: adc: Checkpatch.pl warning cleanups Brian Vandre
2014-10-21  2:48 ` [PATCH 1/2] Staging: iio: adc: fix line over 80 characters Brian Vandre
2014-10-23 10:39   ` Daniel Baluta
2014-10-21  2:48 ` [PATCH 2/2] " Brian Vandre
2014-10-21  7:29 ` [PATCH 0/2] Staging: iio: adc: Checkpatch.pl warning cleanups Alexandre Belloni
2014-10-21 22:56 ` Brian Vandre [this message]
2014-10-21 22:56   ` [PATCH v2] Staging: iio: adc: fix line over 80 characters Brian Vandre
2014-10-22  4:21     ` Sudip Mukherjee
2014-10-22 23:47       ` Hartmut Knaack
2014-10-23  2:02         ` Brian Vandre
2014-10-23  3:23         ` Joe Perches
2014-10-23  9:46         ` Sudip Mukherjee
2014-10-23 10:50       ` Lars-Peter Clausen
2014-10-23 12:42         ` Brian Vandre
2014-10-23 12:53     ` Brian Vandre
2014-10-23 13:27       ` Alexandre Belloni

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=cover.1413931615.git.bvandre@gmail.com \
    --to=bvandre@gmail.com \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marex@denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.