All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Javier M. Mellid" <jmunhoz@igalia.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: Fri, 6 May 2011 14:22:07 -0700	[thread overview]
Message-ID: <20110506212207.GA3222@kroah.com> (raw)
In-Reply-To: <1304702696-9403-1-git-send-email-jmunhoz@igalia.com>

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?

thanks,

greg k-h

  reply	other threads:[~2011-05-06 21:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-06 17:24 [PATCH] staging: sm7xx: Use kernel framebuffer mode setting Javier M. Mellid
2011-05-06 21:22 ` Greg KH [this message]
2011-05-06 22:26   ` Javier Muñoz
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=20110506212207.GA3222@kroah.com \
    --to=greg@kroah.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=jmunhoz@igalia.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.