From: Greg KH <greg@kroah.com>
To: John Sheehan <john.d.sheehan@gmail.com>
Cc: gregkh@suse.de, wfp5p@virginia.edu, roel.kluin@gmail.com,
jkosina@suse.cz, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Staging: comedi: fix code style errors in s626.c
Date: Thu, 17 Jun 2010 13:34:24 -0700 [thread overview]
Message-ID: <20100617203424.GA32523@kroah.com> (raw)
In-Reply-To: <1275060688-18454-1-git-send-email-john.d.sheehan@gmail.com>
On Fri, May 28, 2010 at 04:31:28PM +0100, John Sheehan wrote:
> From: John Sheehan <john.d.sheehan@gmail.com>
>
> A patch for s626.c to fix errors reported by
> checkpatch.pl tool, namely,
> code indent should use tabs where possible
> "foo * bar" should be "foo *bar"
> trailing statements should be on next line
>
> Signed-off-by: John Sheehan <john.d.sheehan@gmail.com>
> ---
> drivers/staging/comedi/drivers/s626.c | 67 +++++++++++++++++++--------------
> 1 files changed, 39 insertions(+), 28 deletions(-)
>
> diff --git a/drivers/staging/comedi/drivers/s626.c b/drivers/staging/comedi/drivers/s626.c
> index a3cc933..83e1bb1 100644
> --- a/drivers/staging/comedi/drivers/s626.c
> +++ b/drivers/staging/comedi/drivers/s626.c
> @@ -60,10 +60,10 @@ INSN_CONFIG instructions:
> insn.insn=INSN_CONFIG; //configuration instruction
> insn.n=1; //number of operation (must be 1)
> insn.data=&initialvalue; //initial value loaded into encoder
> - //during configuration
> + //during configuration
Why change this?
> insn.subdev=5; //encoder subdevice
> insn.chanspec=CR_PACK(encoder_channel,0,AREF_OTHER); //encoder_channel
> - //to configure
> + //to configure
Why is this line indented so much now?
Care to resend this without these changes?
thanks,
greg k-h
next prev parent reply other threads:[~2010-06-17 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 15:31 [PATCH 1/2] Staging: comedi: fix code style errors in s626.c John Sheehan
2010-06-17 20:34 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-06-18 17:38 John Sheehan
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=20100617203424.GA32523@kroah.com \
--to=greg@kroah.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=jkosina@suse.cz \
--cc=john.d.sheehan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roel.kluin@gmail.com \
--cc=wfp5p@virginia.edu \
/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