mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Indan Zupancic" <indan@nul.nu>
To: "Chris Wilson" <chris@chris-wilson.co.uk>
Cc: "Michal Hocko" <mhocko@suse.cz>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	dri-devel@lists.freedesktop.org
Subject: Re: Linux 2.6.37
Date: Thu, 13 Jan 2011 01:35:35 +0100 (CET)	[thread overview]
Message-ID: <75cb3b3e624d2daf7c9a414e50cfcb74.squirrel@webmail.greenhost.nl> (raw)
In-Reply-To: <b9dded$hknqnh@orsmga002.jf.intel.com>

On Wed, January 12, 2011 13:07, Chris Wilson wrote:
>
> Sure, s/intel_panel_get_max_backlight/intel_panel_get_backlight/ and we
> get the behaviour we both want - preserving the current backlight unless
> none is set.

Indeed, I hadn't noticed that shortcut. That's a lot nicer than my ifdefery.

>
>> While I'm glad this problem is being fixed upstream, it would be nice to get
>> some credit for finding the source of the problem.
>
> Sorry. You found the bug but I felt your rationale was off. However, I was
> amiss in not giving you the credit you fully deserved.

Thank you very much!

The rationale was that intel_panel_set_backlight(0) was somehow called twice,
and that the current code unconditionally stored the old backlight, and thus
losing the original brightness level. This is exactly what happened. My fix
was to prevent backlight_level from being overwritten by zero. Your fix was
more structural and properly fixed backlight enabled/disabled state. In the
end both have the same effect and solve the bug. Perhaps I was unclear in
the bug description.

Anyhow, it's a pleasure working with you. I'll try to not bother you too much,
you got enough on your plate as it is. I'll leave you alone for a while after
you looked into my fix for bug 23472, after that all my Intel graphics are
pretty much solved. :-)

Take care,

Indan



  parent reply	other threads:[~2011-01-13  0:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-05  1:15 Linus Torvalds
2011-01-06 10:48 ` Michal Hocko
2011-01-06 16:29   ` Linus Torvalds
2011-01-06 17:03     ` Michal Hocko
2011-01-06 17:49     ` Chris Wilson
2011-01-06 20:55       ` Alex Riesen
2011-01-06 21:03         ` Chris Wilson
2011-01-06 21:08         ` Alex Riesen
2011-01-07 15:52           ` Michal Hocko
2011-01-11 13:33   ` Pavel Machek
2011-01-11 14:28     ` Michal Hocko
2011-01-11 14:47     ` Alex Riesen
2011-01-11 17:19   ` Michal Hocko
2011-01-11 17:37     ` Michal Hocko
2011-01-11 18:37       ` Michal Hocko
2011-01-11 17:39     ` Chris Wilson
2011-01-11 17:44       ` Michal Hocko
2011-01-12  0:35       ` Indan Zupancic
2011-01-12 12:07         ` Chris Wilson
2011-01-12 12:14           ` Chris Wilson
2011-01-13  0:35           ` Indan Zupancic [this message]
2011-01-07 19:20 Zephaniah E. Loss-Cutler-Hull

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=75cb3b3e624d2daf7c9a414e50cfcb74.squirrel@webmail.greenhost.nl \
    --to=indan@nul.nu \
    --cc=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®