From: Greg KH <gregkh@linuxfoundation.org>
To: Chase Southwood <chase.southwood@yahoo.com>
Cc: devel@driverdev.osuosl.org, abbotti@mev.co.uk,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3 v2] Staging: comedi: addi-data: fix a couple of lines that are too long
Date: Mon, 24 Feb 2014 17:00:39 -0800 [thread overview]
Message-ID: <20140225010039.GA31031@kroah.com> (raw)
In-Reply-To: <1393259709-18516-1-git-send-email-chase.southwood@yahoo.com>
On Mon, Feb 24, 2014 at 10:35:09AM -0600, Chase Southwood wrote:
> There are a couple of cases where a comment being on the same line as a
> statement is causing the line to be over 80 characters long. This is an
> easy fix, move these comments to the previous line.
>
> Signed-off-by: Chase Southwood <chase.southwood@yahoo.com>
> Reviewed-by: Ian Abbott <abbotti@mev.co.uk>
>
> ---
> 2: Some changes to PATCH 2/3 v2 occurred in the immediate context of
> changes in this patch. I've redone this patch after updating PATCH 2/3
> so that it still applies cleanly.
Thank you for noticing and fixing this up before I hit it, much
appreciated.
greg k-h
next prev parent reply other threads:[~2014-02-25 0:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-22 3:20 [PATCH 1/3] Staging: comedi: addi-data: comment cleanup in hwdrv_apci035.c Chase Southwood
2014-02-22 3:21 ` [PATCH 2/3] Staging: comedi: addi-data: cleanup conditional blocks " Chase Southwood
2014-02-24 14:13 ` Ian Abbott
2014-02-24 16:00 ` Chase Southwood
2014-02-24 16:34 ` [PATCH 2/3 v2] " Chase Southwood
2014-02-24 16:40 ` Ian Abbott
2014-02-22 3:21 ` [PATCH 3/3] Staging: comedi: addi-data: fix a couple of lines that are too long Chase Southwood
2014-02-24 14:14 ` Ian Abbott
2014-02-24 16:35 ` [PATCH 3/3 v2] " Chase Southwood
2014-02-24 16:41 ` Ian Abbott
2014-02-25 1:00 ` Greg KH [this message]
2014-02-24 14:08 ` [PATCH 1/3] Staging: comedi: addi-data: comment cleanup in hwdrv_apci035.c Ian Abbott
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=20140225010039.GA31031@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=abbotti@mev.co.uk \
--cc=chase.southwood@yahoo.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
/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