From: James Simmons <jsimmons@infradead.org>
To: linux-fbdev@vger.kernel.org
Subject: Re: [fwd: [PATCH] obsolete config in kernel source
Date: Fri, 05 Feb 2010 15:14:51 +0000	[thread overview]
Message-ID: <alpine.LFD.2.00.1002051513060.23086@casper.infradead.org> (raw)
In-Reply-To: <20100120111628.GA2040@stud.informatik.uni-erlangen.de>
> ----- Forwarded message from Christoph Egger <siccegge@stud.informatik.uni-erlangen.de> -----
> 
> Date: Fri, 15 Jan 2010 13:27:56 +0100
> 
> Hi all!
> 
> 	As part of the VAMOS[0] research project at the University of
> Erlangen we're checking referential integrity between kernel KConfig
> options and in-code Conditional blocks.
> 
> 	While probably not strictly a integrity violation (as
> FB_SOFT_CURSOR can still be set as it is once mentioned in a KConfig
> select statement this looks like a left-over of
> c465e05a03209651078b95686158648fd7ed84c5
> 
> 	Please keep me informed of this patch getting confirmed /
> merged so we can keep track of it.
> 
> Regards
> 
> 	Christoph Egger
> 
> [0] http://vamos1.informatik.uni-erlangen.de/
> 
> >From 5461c8d1ebc54e9f5c86233aa831cefc7c06a140 Mon Sep 17 00:00:00 2001
> From: Christoph Egger <siccegge@stud.informatik.uni-erlangen.de>
> Date: Fri, 15 Jan 2010 11:03:50 +0100
> Subject: [PATCH] Clean missed bit of FB_SOFT_CURSOR
> 
> While the config Option FB_SOFT_BUFFER was removed in
> c465e05a03209651078b95686158648fd7ed84c5 while moving to fbcon this
> single driver has it left as a select in KConfig / #ifdef in
> source. This last occurence is removed here so the option is really
> gone
> 
> Signed-off-by: Christoph Egger <siccegge@stud.informatik.uni-erlangen.de>
Acked-by: James Simmons <jsimmons@infradead.org>
Patches is fine.
>  drivers/video/Kconfig        |    1 -
>  drivers/video/sis/sis_main.c |    3 ---
>  2 files changed, 0 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/video/Kconfig b/drivers/video/Kconfig
> index 5a5c303..7fe1839 100644
> --- a/drivers/video/Kconfig
> +++ b/drivers/video/Kconfig
> @@ -1494,7 +1494,6 @@ config FB_VIA
>         select FB_CFB_FILLRECT
>         select FB_CFB_COPYAREA
>         select FB_CFB_IMAGEBLIT
> -       select FB_SOFT_CURSOR
>         select I2C_ALGOBIT
>         select I2C
>         help
> diff --git a/drivers/video/sis/sis_main.c b/drivers/video/sis/sis_main.c
> index 9d2b6bc..a531a0f 100644
> --- a/drivers/video/sis/sis_main.c
> +++ b/drivers/video/sis/sis_main.c
> @@ -1891,9 +1891,6 @@ static struct fb_ops sisfb_ops = {
>  	.fb_fillrect	= fbcon_sis_fillrect,
>  	.fb_copyarea	= fbcon_sis_copyarea,
>  	.fb_imageblit	= cfb_imageblit,
> -#ifdef CONFIG_FB_SOFT_CURSOR
> -	.fb_cursor	= soft_cursor,
> -#endif
>  	.fb_sync	= fbcon_sis_sync,
>  #ifdef SIS_NEW_CONFIG_COMPAT
>  	.fb_compat_ioctl= sisfb_ioctl,
> -- 
> 1.6.3.3
> 
> 
> 
> ----- End forwarded message -----
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
     prev parent reply	other threads:[~2010-02-05 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-20 11:16 [Fwd: [PATCH] obsolete config in kernel source (FB_SOFT_CURSOR)] Christoph Egger
2010-01-27  9:44 ` [fwd: " Christoph Egger
2010-02-05 15:14 ` James Simmons [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=alpine.LFD.2.00.1002051513060.23086@casper.infradead.org \
    --to=jsimmons@infradead.org \
    --cc=linux-fbdev@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).