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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20110506235544.GC22803@suse.de>
Date:	Fri, 6 May 2011 16:55:44 -0700
From:	Greg KH <gregkh@...e.de>
To:	Javier Muñoz <jmunhoz@...lia.com>
Cc:	Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org,
	devel@...verdev.osuosl.org
Subject: Re: [PATCH] staging: sm7xx: Use kernel framebuffer mode setting

On Sat, May 07, 2011 at 12:26:49AM +0200, Javier Muñoz wrote:
> On 05/06/2011 11:22 PM, Greg KH wrote:
> >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?
> 
> Sorry, I didn't know. I made this patch against
> linux-2.6 (bfd412db9e7b0d8f7b9c09d12d07aa2ac785f1d0) as I did with
> previous patches.
> 
> Testing was about creating, applying, compiling and running patch
> with kernel built from linux-2.6
> 
> Do you need a new patch against linux-next's master? I can redo this patch.

Yes, please always make patches against linux-next as it includes any
other pending patches that are in my tree.

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/