All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg@redhat.com>
To: Ali Gholami Rudi <ali@rudi.ir>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Keith Packard <keithp@keithp.com>,
	Michel Alexandre Salim <salimma@fedoraproject.org>,
	intel-gfx@lists.freedesktop.org,
	Ali Gholami Rudi <aliqrudi@gmail.com>,
	Richard Purdie <rpurdie@rpsys.net>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	David Airlie <airlied@linux.ie>,
	Alex Deucher <alexdeucher@gmail.com>,
	Ben Skeggs <bskeggs@redhat.com>, Zhang Rui <rui.zhang@intel.com>,
	Len Brown <lenb@kernel.org>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	Sedat Dilek <sedat.dilek@googlemail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: missing acpi backlight bisected to 9661e92c10
Date: Thu, 11 Aug 2011 15:16:30 +0100	[thread overview]
Message-ID: <20110811141630.GA24704@srcf.ucam.org> (raw)
In-Reply-To: <20112108181410@lilem.mirepesht>

Well, that all looks fine. And I also can't see any way that this commit
could cause the backlight not to appear - all it does is set the parent 
if it's present. There's no new path that could cause it to return 
early. Does reverting this patch really make things work?

-- 
Matthew Garrett | mjg59@srcf.ucam.org

WARNING: multiple messages have this Message-ID (diff)
From: Matthew Garrett <mjg@redhat.com>
To: Ali Gholami Rudi <ali@rudi.ir>
Cc: David Airlie <airlied@linux.ie>,
	linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org,
	Sedat Dilek <sedat.dilek@googlemail.com>,
	Richard Purdie <rpurdie@rpsys.net>,
	Ben Skeggs <bskeggs@redhat.com>,
	Michel Alexandre Salim <salimma@fedoraproject.org>,
	Alex Deucher <alexdeucher@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Len Brown <lenb@kernel.org>
Subject: Re: missing acpi backlight bisected to 9661e92c10
Date: Thu, 11 Aug 2011 15:16:30 +0100	[thread overview]
Message-ID: <20110811141630.GA24704@srcf.ucam.org> (raw)
In-Reply-To: <20112108181410@lilem.mirepesht>

Well, that all looks fine. And I also can't see any way that this commit
could cause the backlight not to appear - all it does is set the parent 
if it's present. There's no new path that could cause it to return 
early. Does reverting this patch really make things work?

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2011-08-11 14:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-08 18:54 i915 native backlight never got merged Kamal Mostafa
2011-08-08 21:27 ` Keith Packard
2011-08-08 21:31   ` Matthew Garrett
2011-08-08 22:43     ` Keith Packard
2011-08-10 13:14       ` Michel Alexandre Salim
2011-08-10 14:53         ` Keith Packard
2011-08-11  2:17           ` Andrew Morton
2011-08-11  4:22             ` Ali Gholami Rudi
     [not found]               ` <20112108160718@lilem.mirepesht>
2011-08-11 12:39                 ` missing acpi backlight bisected to 9661e92c10 Matthew Garrett
2011-08-11 13:53                   ` Ali Gholami Rudi
2011-08-21 13:52                     ` Ali Gholami Rudi
2011-08-11 14:16                     ` Matthew Garrett [this message]
2011-08-11 14:16                       ` Matthew Garrett
2011-08-11 14:27                       ` Ali Gholami Rudi
2011-08-21 14:21                         ` Ali Gholami Rudi
     [not found]                         ` <20112208102524@lilem.mirepesht>
2011-08-12 12:18                           ` Matthew Garrett
2011-08-12 12:49                             ` Ali Gholami Rudi
2011-08-22 12:40                               ` Ali Gholami Rudi
2011-08-11 19:36               ` i915 native backlight never got merged Michel Alexandre Salim
2011-08-11 22:28                 ` Keith Packard
2011-08-12  4:21                   ` Kamal Mostafa
2011-08-12 10:11                   ` Michel Alexandre Salim
2011-08-12 13:52                     ` Keith Packard
2011-08-12 16:34                       ` Kamal Mostafa
2011-08-15 17:38                         ` Michel Alexandre Salim
2011-08-15 18:03                           ` Keith Packard

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=20110811141630.GA24704@srcf.ucam.org \
    --to=mjg@redhat.com \
    --cc=airlied@linux.ie \
    --cc=akpm@linux-foundation.org \
    --cc=alexdeucher@gmail.com \
    --cc=ali@rudi.ir \
    --cc=aliqrudi@gmail.com \
    --cc=bskeggs@redhat.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=keithp@keithp.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    --cc=rui.zhang@intel.com \
    --cc=salimma@fedoraproject.org \
    --cc=sedat.dilek@googlemail.com \
    --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 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.