All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Alberto Panizzo <maramaopercheseimorto@gmail.com>
Cc: Sascha linux-arm <s.hauer@pengutronix.de>,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	Dan Williams <dan.j.williams@intel.com>,
	Krzysztof Helt <krzysztof.h1@wp.pl>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mx3fb: some debug and initialisation fixes.
Date: Tue, 26 Jan 2010 13:46:57 -0800	[thread overview]
Message-ID: <20100126134657.4cc543a6.akpm@linux-foundation.org> (raw)
In-Reply-To: <1263999434.3083.44.camel@realization>

On Wed, 20 Jan 2010 15:57:14 +0100
Alberto Panizzo <maramaopercheseimorto@gmail.com> wrote:

> Fix the kernel oops when dev_dbg is called with mx3_fbi->txd == NULL
> 
> Fix the late initialisation of mx3fb->backlight_level.
> If not, in the chain of function started by init_fb_chan(), in __blank() call 
> sdc_set_brightness(mx3fb, mx3fb->backlight_level) that will shut down
> the CONTRAST PWM output. 

I guess these aren't the biggest bugs we ever had but I tagged the
patch for backporting into 2.6.32.x anyway - the fixes are prety
obvious.

Your email client replaces tabs with spaces.  I fixed that up, but
please do prevent it from happening next time. 
Documentation/email-clients.txt has some Evolution tips.


  reply	other threads:[~2010-01-26 21:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-20 14:57 [PATCH] mx3fb: some debug and initialisation fixes Alberto Panizzo
2010-01-26 21:46 ` Andrew Morton [this message]
2010-01-27  9:45   ` Alberto Panizzo
  -- strict thread matches above, loose matches on Subject: below --
2009-12-18 16:04 Alberto Panizzo
2009-12-20 16:45 ` Guennadi Liakhovetski
2010-01-20 11:12   ` Alberto Panizzo
2010-01-20 11:54     ` Mark Brown
2010-01-20 14:43       ` Alberto Panizzo

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=20100126134657.4cc543a6.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=krzysztof.h1@wp.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maramaopercheseimorto@gmail.com \
    --cc=s.hauer@pengutronix.de \
    /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.