All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Payal Kshirsagar <payal.s.kshirsagar.98@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [PATCH] [Outreachy kernel] staging: mxx_udc: remove unused code
Date: Thu, 21 Mar 2019 11:01:39 +0100	[thread overview]
Message-ID: <20190321100139.GD2836@kroah.com> (raw)
In-Reply-To: <1553157183-2879-1-git-send-email-payal.s.kshirsagar.98@gmail.com>

On Thu, Mar 21, 2019 at 02:03:03PM +0530, Payal Kshirsagar wrote:
> Remove the code enclosed by #if 0 and its #endif because that code never
> going to be run
> 
> Signed-off-by: Payal Kshirsagar <payal.s.kshirsagar.98@gmail.com>
> ---
>  drivers/staging/emxx_udc/emxx_udc.h | 7 -------
>  1 file changed, 7 deletions(-)
> 
> diff --git a/drivers/staging/emxx_udc/emxx_udc.h b/drivers/staging/emxx_udc/emxx_udc.h
> index 540e4ca..212aded 100644
> --- a/drivers/staging/emxx_udc/emxx_udc.h
> +++ b/drivers/staging/emxx_udc/emxx_udc.h
> @@ -8,13 +8,6 @@
>  #ifndef _LINUX_EMXX_H
>  #define _LINUX_EMXX_H
>  
> -/*---------------------------------------------------------------------------*/
> -/*----------------- Default undef */
> -#if FALSE
> -#define DEBUG
> -#define UDC_DEBUG_DUMP
> -#endif

The reason this is here is to make it "easy" for a developer to enable
debugging for the driver.

Now we should just rely on the in-kernel dynamic debugging support, so
we should be able to get rid of this, but before you do that, you need
to remove the use of those two #defines on the codebase.

So for now, please leave this as-is.

thanks,

greg k-h


  reply	other threads:[~2019-03-21 10:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21  8:33 [PATCH] [Outreachy kernel] staging: mxx_udc: remove unused code Payal Kshirsagar
2019-03-21 10:01 ` Greg KH [this message]
2019-03-21 10:08   ` Payal Kshirsagar

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=20190321100139.GD2836@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=payal.s.kshirsagar.98@gmail.com \
    /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.