From: Greg KH <gregkh@suse.de>
To: supermine290 <supermine290@gmail.com>
Cc: Bill Pemberton <wfp5p@virginia.edu>,
Shawn Bohrer <shawn.bohrer@gmail.com>,
Frank Mori Hess <fmhess@users.sourceforge.net>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: Patch to comedi_fops.c
Date: Mon, 29 Mar 2010 08:19:04 -0700 [thread overview]
Message-ID: <20100329151904.GB12015@suse.de> (raw)
In-Reply-To: <4BB03C13.7090209@gmail.com>
On Mon, Mar 29, 2010 at 01:35:15AM -0400, supermine290 wrote:
> >From eb3bff4e8052a4075d82f1687e0338dc81d73256 Mon Sep 17 00:00:00 2001
> From: Jakob Penzien <jakob@bloodmoon.(none)>
> Date: Tue, 23 Mar 2010 12:52:14 -0400
> Subject: [PATCH] Staging: comedi: fix space before tab style issue
> in comedi_fops.c
> This is a patch to the comedi_fops.c file that fixes up a tab style
> warning
> found by the checkpathc.pl tool. This patch was done to 2.6.34 kernel.
> Signed-off-by: Jakob Penzien <supermine290@gmail.com>
>
> ---
> drivers/staging/comedi/comedi_fops.c | 38
> +++++++++++++++++-----------------
> 1 files changed, 19 insertions(+), 19 deletions(-)
>
> diff --git a/drivers/staging/comedi/comedi_fops.c
> b/drivers/staging/comedi/comedi_fops.c
> index aca9674..5cb5bc7 100644
> --- a/drivers/staging/comedi/comedi_fops.c
> +++ b/drivers/staging/comedi/comedi_fops.c
> @@ -598,19 +598,19 @@ copyback:
> static int parse_insn(struct comedi_device *dev, struct comedi_insn
> *insn,
The patch is line-wrapped, can you please fix this and resend it?
thanks,
greg k-h
next prev parent reply other threads:[~2010-03-29 15:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 5:35 Patch to comedi_fops.c supermine290
2010-03-29 15:19 ` Greg KH [this message]
2010-04-17 8:23 ` supermine290
-- strict thread matches above, loose matches on Subject: below --
2010-03-23 17:06 supermine290
2010-04-27 22:11 ` Greg KH
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=20100329151904.GB12015@suse.de \
--to=gregkh@suse.de \
--cc=devel@driverdev.osuosl.org \
--cc=fmhess@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shawn.bohrer@gmail.com \
--cc=supermine290@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;
as well as URLs for NNTP newsgroup(s).