From: "Javier Muñoz" <jmunhoz@igalia.com>
To: Greg KH <greg@kroah.com>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH] staging: sm7xx: Use kernel framebuffer mode setting
Date: Sat, 07 May 2011 00:26:49 +0200 [thread overview]
Message-ID: <4DC475A9.8070701@igalia.com> (raw)
In-Reply-To: <20110506212207.GA3222@kroah.com>
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@igalia.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.
Sorry for the inconvenience.
javi
next prev parent reply other threads:[~2011-05-06 22:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 17:24 Javier M. Mellid
2011-05-06 21:22 ` Greg KH
2011-05-06 22:26 ` Javier Muñoz [this message]
2011-05-06 23:55 ` Greg KH
2011-05-07 1:16 ` Javier Muñoz
2011-05-07 1:11 ` [PATCH RESEND 1/1] " Javier M. Mellid
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=4DC475A9.8070701@igalia.com \
--to=jmunhoz@igalia.com \
--cc=devel@driverdev.osuosl.org \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@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
Powered by JetHome