From: Hans de Goede <hdegoede@redhat.com>
To: Darren Hart <dvhart@infradead.org>
Cc: Ben Skeggs <bskeggs@redhat.com>,
platform-driver-x86@vger.kernel.org,
dri-devel@lists.freedesktop.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Aaron Lu <aaron.lu@intel.com>,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH 0/3] Use acpi_video_unregister_backlight instead of acpi_video_unregister in platfrom backlight drivers
Date: Mon, 01 Jun 2015 19:58:17 +0200 [thread overview]
Message-ID: <556C9D39.8030506@redhat.com> (raw)
In-Reply-To: <20150601174103.GC87111@vmdeb7>
Hi Darren,
On 01-06-15 19:41, Darren Hart wrote:
> On Mon, Jun 01, 2015 at 11:25:05AM +0200, Hans de Goede wrote:
>> Hi All,
>>
>> I'm working on cleaning up the currently somewhat convoluted logic to
>> select which backlight interfaces to register on x86 systems, see:
>> http://lists.freedesktop.org/archives/dri-devel/2014-December/074687.html
>>
>> For a rought outline (details will change in the actual patch-set).
>>
>> These 3 patches are a preparation for that work, as the behavior of the
>> current code is not always consistent (it changes depending on module
>> loading order in some cases). These 3 patches remove this inconsistency
>> which in some cases may result in a behavior change.
>>
>> This way the cleanup can have a consistent base to build upon, and I can
>> ensure that the cleanup itself does not cause any functional changes.
>>
>> I hope to post a v1 of the actual cleanup patch-set in 1-2 weeks.
>
> That will likely mean we miss the 4.2 merge window and will target this for 4.3
> (which is fine by me, but just so you know).
IMHO this patches are worthwhile to have by themselves, as said
they fix various inconsistencies, which is a good thing to fix
regardless.
I think that these going into 4.2, and the cleanup which depends on them
(but is other then that pretty much an orthogonal patch set) going into
4.3 is actually a good thing, because if people then experience any
problems due to my work on this, we can easily see if it is due to
the behavior change these 3 patches may introduce in some cases, or
if it is due to the actual cleanup causing a behavior change (which it
should not).
Regards,
Hans
next prev parent reply other threads:[~2015-06-01 17:58 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 [this message]
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
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=556C9D39.8030506@redhat.com \
--to=hdegoede@redhat.com \
--cc=aaron.lu@intel.com \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=dvhart@infradead.org \
--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).