From: Dan Carpenter <dan.carpenter@oracle.com>
To: Jake Champlin <jake.champlin.27@gmail.com>
Cc: abbotti@mev.co.uk, devel@driverdev.osuosl.org,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
fmhess@users.sourceforge.net
Subject: Re: [PATCH] Staging: comedi: ni_tio: Fixed whitespace / spacing issue
Date: Thu, 17 Jan 2013 10:25:23 +0300 [thread overview]
Message-ID: <20130117072523.GJ4584@mwanda> (raw)
In-Reply-To: <20130117010523.GA18848@gmail.com>
On Wed, Jan 16, 2013 at 08:05:28PM -0500, Jake Champlin wrote:
> Fixed a leading whitespace coding style issue.
>
> Signed-off-by: Jake Champlin <jake.champlin.27@gmail.com>
> ---
> drivers/staging/comedi/drivers/ni_tio.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/comedi/drivers/ni_tio.c b/drivers/staging/comedi/drivers/ni_tio.c
> index 98f8789..73e7cbe 100644
> --- a/drivers/staging/comedi/drivers/ni_tio.c
> +++ b/drivers/staging/comedi/drivers/ni_tio.c
> @@ -276,7 +276,7 @@ static inline unsigned NI_660x_RTSI_Second_Gate_Select(unsigned n)
> }
>
> static const unsigned int counter_status_mask =
> - COMEDI_COUNTER_ARMED | COMEDI_COUNTER_COUNTING;
> +COMEDI_COUNTER_ARMED | COMEDI_COUNTER_COUNTING;
No. It should be intended but just using tabs instead of spaces.
regards,
dan carpenter
>
> static int __init ni_tio_init_module(void)
> {
> --
> 1.8.1.1
>
>
> --
> Jake Champlin
> jake.champlin.27@gmail.com
> 8123742937
> <MuttClient>
> _______________________________________________
> devel mailing list
> devel@linuxdriverproject.org
> http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
prev parent reply other threads:[~2013-01-17 7:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 1:05 [PATCH] Staging: comedi: ni_tio: Fixed whitespace / spacing issue Jake Champlin
2013-01-17 7:25 ` Dan Carpenter [this message]
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=20130117072523.GJ4584@mwanda \
--to=dan.carpenter@oracle.com \
--cc=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=fmhess@users.sourceforge.net \
--cc=gregkh@linuxfoundation.org \
--cc=jake.champlin.27@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).