From: Andrew Morton <akpm@linux-foundation.org>
To: sedat.dilek@gmail.com
Cc: Sedat Dilek <sedat.dilek@googlemail.com>,
Matthew Garrett <mjg@redhat.com>,
DRI <dri-devel@lists.freedesktop.org>,
intel-gfx@lists.freedesktop.org,
LKML <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH 2/5] i915: Add native backlight control
Date: Thu, 20 Jan 2011 21:55:02 -0800 [thread overview]
Message-ID: <20110120215502.2305532b.akpm@linux-foundation.org> (raw)
In-Reply-To: <AANLkTimogiJMKkcgfOCJHxpyZHcB36+xzRFgkqWPOiv_@mail.gmail.com>
On Fri, 21 Jan 2011 06:36:54 +0100 Sedat Dilek <sedat.dilek@googlemail.com> wrote:
> ( Original posting from [1] )
>
> I have the backlight-type patchset for months in my patch-series (and
> maintained them if necessary against daily linux-next).
> Also the last series from 14-Jan-2011 (see 1-5 patch from [2] and the
> following ones at dri-devel ML).
>
> If you couldn't find the updated v2 radeon-backlight-type patch, here
> the extract from my patch-series:
> ...
> # Patch from <https://patchwork.kernel.org/patch/491351/>
> + backlight-type/v2-drm-radeon-kms-Expose-backlight-class-device-for-legacy-LVDS-encoder.patch
> ...
>
> I can only speak for the radeon(-KMS) part with
> CONFIG_BACKLIGHT_CLASS_DEVICE=y set and against linux-next: It worked,
> it works.
>
> I am a bit angry that someone of the "big 5" gets immediately an
> answer where mine is ignored [3].
Well, who were they sent to?
If it was dri-devel then perhaps the people there felt it was
inappropriate to their tree, or they were all busy fixing
100000000000000 regressions.
If it was Richard then he's been distracted by other things for some
time, which is why I recently started handling backlight and leds
patches.
If it was me then kick me, but I don't think it was.
In general, if you think that patches aren't getting attention then let
me know and send them to me - harassing people for you is part of my
job description.
> So dear Mr. AKPM, if you can standstill for a few moments to answer
> only one of my questions, through which kernel-tree will this patchset
> walk trough?
leds and backlight patches are presently getting merged into my tree
and I'm sending them into Linus. I make sure that Richard sees them
all and when he finds time he helps review them for us.
They should turn up in linux-next too - we're working on that.
This particular patch series is theoretically a bit late for 2.6.38,
but if anyone thinks that's a wrong decision, feel free to explain why.
next prev parent reply other threads:[~2011-01-21 5:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 5:36 [Intel-gfx] [PATCH 2/5] i915: Add native backlight control Sedat Dilek
2011-01-21 5:55 ` Andrew Morton [this message]
2011-01-21 9:04 ` Sedat Dilek
-- strict thread matches above, loose matches on Subject: below --
2011-01-14 19:24 [PATCH 1/5] Backlight: Add backlight type Matthew Garrett
2011-01-14 19:24 ` [PATCH 2/5] i915: Add native backlight control Matthew Garrett
2011-01-20 20:30 ` [Intel-gfx] " Ali Gholami Rudi
[not found] ` <20112101004346@lilem.mirepesht>
2011-01-20 23:13 ` Andrew Morton
2011-01-21 0:43 ` Matthew Garrett
2011-01-21 1:03 ` Andrew Morton
2011-01-21 4:57 ` Matthew Garrett
2011-01-23 4:45 ` Ali Gholami Rudi
2011-01-23 4:56 ` Matthew Garrett
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=20110120215502.2305532b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=sedat.dilek@gmail.com \
--cc=sedat.dilek@googlemail.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 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).