From: Richard Purdie <rpurdie@rpsys.net>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: "Thadeu Lima de Souza Cascardo" <cascardo@holoscopio.com>,
"Bruno Prémont" <bonbons@linux-vserver.org>,
"Daniel Oliveira Nascimento" <don@syst.com.br>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] backlight, classmate-laptop: fix missing registration failure handling
Date: Fri, 26 Feb 2010 16:45:16 +0000 [thread overview]
Message-ID: <1267202716.16022.34.camel@rex> (raw)
In-Reply-To: <20100226163241.GA20002@srcf.ucam.org>
On Fri, 2010-02-26 at 16:32 +0000, Matthew Garrett wrote:
> If Richard applies my patch to rework backlight registration, this won't
> apply. Richard, what's the situation there?
Your patch has priority, publishing new patches at this point in time is
getting a bit late.
Cheers,
Richard
next prev parent reply other threads:[~2010-02-26 16:45 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-20 23:10 [Patch 0/3] backlight Bruno Prémont
2010-02-20 23:18 ` [PATCH 2/3] backlight: mark struct backlight_ops const Bruno Prémont
2010-02-22 19:35 ` Mike Frysinger
2010-02-26 11:56 ` [PATCH] " Bruno Prémont
2010-02-20 23:20 ` [PATCH 1/3] backlight: Add backlight_device parameter to check_fb Bruno Prémont
2010-02-24 16:00 ` [PATCH 1/3] picolcd: driver for PicoLCD HID device Bruno Prémont
[not found] ` <20100224163101.3622d69f@neptune.home>
2010-02-24 16:01 ` [PATCH 2/3] hid: add suspend/resume hooks for hid drivers Bruno Prémont
2010-02-25 4:19 ` Oliver Neukum
2010-02-25 10:12 ` Bruno Prémont
2010-02-24 16:01 ` [PATCH 3/3] hid-picolcd: make use of new suspend/resume hooks Bruno Prémont
2010-02-24 18:27 ` [PATCH 1/3] picolcd: driver for PicoLCD HID device Oliver Neukum
2010-02-24 21:44 ` Rick L. Vinyard, Jr.
2010-02-25 4:11 ` Oliver Neukum
2010-02-25 11:00 ` Jiri Kosina
2010-02-25 15:34 ` Rick L. Vinyard, Jr.
2010-02-26 8:12 ` Dmitry Torokhov
2010-02-25 11:07 ` Jiri Kosina
2010-02-25 11:32 ` Bruno Prémont
2010-02-25 15:18 ` Jiri Kosina
2010-02-25 15:29 ` Bruno Prémont
2010-03-13 19:39 ` Bruno Prémont
2010-03-13 21:35 ` Alan Stern
2010-03-13 22:13 ` [PATCH] hid: Register debugfs entries before adding device Bruno Prémont
2010-03-15 13:48 ` Jiri Kosina
2010-02-25 17:52 ` [PATCH 1/3] picolcd: driver for PicoLCD HID device Rick L. Vinyard, Jr.
2010-02-26 8:15 ` Dmitry Torokhov
2010-03-03 6:04 ` Pavel Machek
2010-02-26 11:53 ` [PATCH] backlight: Add backlight_device parameter to check_fb Bruno Prémont
2010-02-20 23:28 ` [PATCH 3/3] backlight: fix missing/incomplete registration failure handling Bruno Prémont
2010-02-21 8:04 ` Harald Welte
2010-02-21 13:35 ` Thadeu Lima de Souza Cascardo
2010-02-24 15:33 ` Anisse Astier
2010-02-26 11:59 ` [PATCH] backlight, classmate-laptop: fix missing " Bruno Prémont
2010-02-26 16:20 ` Thadeu Lima de Souza Cascardo
2010-02-26 16:32 ` Matthew Garrett
2010-02-26 16:45 ` Richard Purdie [this message]
2010-02-26 22:25 ` Bruno Prémont
2010-02-26 12:02 ` [PATCH] backlight, appledisplay: fix incomplete " Bruno Prémont
2010-02-26 12:04 ` [PATCH] backlight, blackfin: fix missing " Bruno Prémont
2010-02-26 12:17 ` [PATCH] backlight, msi-laptop, msi-wmi: fix incomplete " Bruno Prémont
2010-02-26 12:20 ` [PATCH] backlight, panasonic-laptop: " Bruno Prémont
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=1267202716.16022.34.camel@rex \
--to=rpurdie@rpsys.net \
--cc=bonbons@linux-vserver.org \
--cc=cascardo@holoscopio.com \
--cc=don@syst.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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