linux-kernel - Re: [PATCH] staging: sm7xx: Use kernel framebuffer mode setting

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110506212207.GA3222@kroah.com>
Date:	Fri, 6 May 2011 14:22:07 -0700
From:	Greg KH <greg@...ah.com>
To:	"Javier M. Mellid" <jmunhoz@...lia.com>
Cc:	gregkh@...e.de, linux-kernel@...r.kernel.org,
	devel@...verdev.osuosl.org
Subject: Re: [PATCH] staging: sm7xx: Use kernel framebuffer mode setting

On Fri, May 06, 2011 at 07:24:56PM +0200, Javier M. Mellid wrote:
> This patch implements dynamic framebuffer mode setting.
> 
> Previous code works with mode setting in a hard code way. Previous hard
> code configuration is used as default configuration if dynamic mode
> setting or boot mode setting (via sm712vga_setup) is not used.
> 
> Tested with SM712 supporting 1024x600x16 as default hardware resolution.
> 
> Changes:
> 
> - Implement fb_check_var and fb_set_par callbacks
> - Remove __maybe_unused decorator in function being used (sm712vga_setup)
> - Minor cleanup on initialization structs related with mode settings
> - Updated author copyright
> - Updated TODO file
> 
> Signed-off-by: Javier M. Mellid <jmunhoz@...lia.com>
> ---
>  drivers/staging/sm7xx/TODO     |    1 -

This applies with fuzz, this leads me to believe that you didn't test
this on the latest linux-next tree, right?

What did you make this patch against?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/