All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Ravishankar <ravishankarkm32@gmail.com>
Cc: wfp5p@virginia.edu, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org,
	Ravishankar <ravi.shankar@greenturtles.in>
Subject: Re: [PATCH 2/2] Staging: comedi: fix WARNING issue in icp_multi.c
Date: Wed, 6 Jul 2011 08:59:39 -0700	[thread overview]
Message-ID: <20110706155939.GC16625@suse.de> (raw)
In-Reply-To: <1309934026-2677-1-git-send-email-ravishankarkm32@gmail.com>

On Wed, Jul 06, 2011 at 12:03:46PM +0530, Ravishankar wrote:
> From: Ravishankar <ravi.shankar@greenturtles.in>
> 
> This is a patch to the icp_multi.c file that fixes up a WARNING found by the checkpatch.pl tool

What warning?

> 
> Signed-off-by: Ravishankar <ravishankarkm32@gmail.com>
> ---
>  drivers/staging/comedi/drivers/icp_multi.c |   13 ++++++-------
>  1 files changed, 6 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/staging/comedi/drivers/icp_multi.c b/drivers/staging/comedi/drivers/icp_multi.c
> index 126550f..78f33e7 100644
> --- a/drivers/staging/comedi/drivers/icp_multi.c
> +++ b/drivers/staging/comedi/drivers/icp_multi.c
> @@ -59,13 +59,12 @@ Options:
>  #include "icp_multi.h"
>  
>  #define DEVICE_ID	0x8000	/* Device ID */
> +#define ICP_MULTI_EXTDEBUG	/*       */
>  
> -#define ICP_MULTI_EXTDEBUG
> +/* Hardware types of the cards */
> +#define TYPE_ICP_MULTI 0
>  
> -/*  Hardware types of the cards */
> -#define TYPE_ICP_MULTI	0
> -
> -#define IORANGE_ICP_MULTI 	32
> +#define IORANGE_ICP_MULTI 32

These changes did not fix up any "warning", why did you make them?

greg k-h

      reply	other threads:[~2011-07-06 16:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <[PATCH]Staging: comedi: fix tab space warning issues in icp_multi.c>
2011-07-06  6:33 ` [PATCH 2/2] Staging: comedi: fix WARNING issue in icp_multi.c Ravishankar
2011-07-06 15:59   ` Greg KH [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=20110706155939.GC16625@suse.de \
    --to=gregkh@suse.de \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ravi.shankar@greenturtles.in \
    --cc=ravishankarkm32@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 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.