linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Michael Opdenacker <michael.opdenacker@free-electrons.com>
Cc: plagnioj@jcrosoft.com, linux-fbdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers/video: remove unused parameter in Kconfig
Date: Fri, 26 Jul 2013 08:41:47 +0000	[thread overview]
Message-ID: <51F2364B.6090605@ti.com> (raw)
In-Reply-To: <1373259806-23067-1-git-send-email-michael.opdenacker@free-electrons.com>

[-- Attachment #1: Type: text/plain, Size: 1123 bytes --]

On 08/07/13 08:03, Michael Opdenacker wrote:
> This patch proposes to remove the FB_NUC900_DEBUG kernel configuration
> parameter defined in drivers/video/Kconfig, but used nowhere
> in the makefiles and source code.
> 
> Signed-off-by: Michael Opdenacker <michael.opdenacker@free-electrons.com>
> ---
>  drivers/video/Kconfig | 7 -------
>  1 file changed, 7 deletions(-)
> 
> diff --git a/drivers/video/Kconfig b/drivers/video/Kconfig
> index 2e937bd..a9c0964 100644
> --- a/drivers/video/Kconfig
> +++ b/drivers/video/Kconfig
> @@ -2098,13 +2098,6 @@ config GPM1040A0_320X240
>          bool "Giantplus Technology GPM1040A0 320x240 Color TFT LCD"
>          depends on FB_NUC900
>  
> -config FB_NUC900_DEBUG
> -        bool "NUC900 lcd debug messages"
> -        depends on FB_NUC900
> -        help
> -          Turn on debugging messages. Note that you can set/unset at run time
> -          through sysfs
> -
>  config FB_SM501
>  	tristate "Silicon Motion SM501 framebuffer support"
>  	depends on FB && MFD_SM501
> 

Thanks, I've applied this into my 3.12/fbdev branch.

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

      reply	other threads:[~2013-07-26  8:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08  5:03 [PATCH] drivers/video: remove unused parameter in Kconfig Michael Opdenacker
2013-07-26  8:41 ` Tomi Valkeinen [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=51F2364B.6090605@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.opdenacker@free-electrons.com \
    --cc=plagnioj@jcrosoft.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 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).