From: Aaron Lu <aaron.lu@intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
Darren Hart <dvhart@infradead.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
dri-devel@lists.freedesktop.org,
platform-driver-x86@vger.kernel.org, linux-acpi@vger.kernel.org,
Ben Skeggs <bskeggs@redhat.com>
Subject: Re: [PATCH 0/3] Use acpi_video_unregister_backlight instead of acpi_video_unregister in platfrom backlight drivers
Date: Wed, 3 Jun 2015 08:31:00 +0800 [thread overview]
Message-ID: <20150603003100.GA3562@aaronlu.sh.intel.com> (raw)
In-Reply-To: <20150602143350.GB367@aaronlu.sh.intel.com>
On Tue, Jun 02, 2015 at 10:33:50PM +0800, Aaron Lu wrote:
> On Tue, Jun 02, 2015 at 12:14:28PM +0200, Hans de Goede wrote:
> >
> > If this makes sense (*) then the cooling device stuff should maybe moved
> > from the acpi/video.c code to the backlight core code.
>
> It's just a specific driver that provides thermal capability, no need to
> move to the core code.
I didn't get this when replying and now I think it's doable.
Regards,
Aaron
next prev parent reply other threads:[~2015-06-03 0:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 9:25 [PATCH 0/3] Use acpi_video_unregister_backlight instead of acpi_video_unregister in platfrom backlight drivers Hans de Goede
2015-06-01 9:25 ` [PATCH 1/3] apple_gmux: Use acpi_video_unregister_backlight instead of acpi_video_unregister Hans de Goede
2015-06-01 9:25 ` [PATCH 2/3] asus-wmi: " Hans de Goede
2015-06-04 14:42 ` Corentin Chary
2015-06-01 9:25 ` [PATCH 3/3] samsung-laptop: " Hans de Goede
2015-06-04 14:43 ` Corentin Chary
2015-06-01 17:41 ` [PATCH 0/3] Use acpi_video_unregister_backlight instead of acpi_video_unregister in platfrom backlight drivers Darren Hart
2015-06-01 17:58 ` Hans de Goede
2015-06-02 9:59 ` Jani Nikula
2015-06-02 10:14 ` Hans de Goede
2015-06-02 14:33 ` Aaron Lu
2015-06-03 0:31 ` Aaron Lu [this message]
2015-06-02 14:28 ` Aaron Lu
2015-06-03 3:46 ` Darren Hart
2015-06-08 4:54 ` Darren Hart
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=20150603003100.GA3562@aaronlu.sh.intel.com \
--to=aaron.lu@intel.com \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=dvhart@infradead.org \
--cc=hdegoede@redhat.com \
--cc=jani.nikula@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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;
as well as URLs for NNTP newsgroup(s).