From: Richard Purdie <rpurdie@rpsys.net>
To: Matthew Garrett <mjg@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] backlight: Provide two stage registration
Date: Tue, 15 Sep 2009 20:18:42 +0100 [thread overview]
Message-ID: <1253042322.30165.52.camel@dax.rpnet.com> (raw)
In-Reply-To: <1253031583-11286-1-git-send-email-mjg@redhat.com>
On Tue, 2009-09-15 at 17:19 +0100, Matthew Garrett wrote:
> The backlight class currently allocates and registers a backlight device
> in a single function, making it impossible for certain backlight parameters
> to be set before the device becomes visible to userspace. This can cause
> problems if userspace wins the race and manages to read any of these values
> before they've been set, and also makes it harder to extend information
> that we may wish to provide to the rest of the kernel at registration time.
>
> This patch breaks the register and unregister functions into two,
> separating allocation and registration. The old functions are left to ease
> transition.
I understand the problem but the second patch in this series bothers me
- an additional 300 lines of error handling in each driver.
Could we not pass an optional pointer to a properties structure to
create the backlight with instead or find a better way to solve this?
Cheers,
Richard
--
Richard Purdie
Intel Open Source Technology Centre
next prev parent reply other threads:[~2009-09-15 19:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 16:19 [PATCH 1/3] backlight: Provide two stage registration Matthew Garrett
2009-09-15 16:19 ` [PATCH 2/3] backlight: Transition drivers to new backlight API Matthew Garrett
2009-09-15 16:19 ` [PATCH 3/3] backlight: Remove old device_register and device_unregister API Matthew Garrett
2009-09-15 19:18 ` Richard Purdie [this message]
2009-09-15 19:27 ` [PATCH 1/3] backlight: Provide two stage registration Matthew Garrett
2009-09-15 19:42 ` Richard Purdie
2009-09-16 2:22 ` Henrique de Moraes Holschuh
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=1253042322.30165.52.camel@dax.rpnet.com \
--to=rpurdie@rpsys.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
/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.