LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Thomas Renninger <trenn@suse.de>,
	toshiba_acpi@memebeam.org, linux-acpi@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ACPI video.c brightness handler conflicts with toshiba_acpi
Date: Fri, 07 Nov 2008 22:29:53 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0811072224200.9051@localhost.localdomain> (raw)
In-Reply-To: <200810281922.20490.arvidjaar@mail.ru>



> > Do you have a pointer to those patches?
> > 
> 
> So far I am running with these commits from git://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-acpi-2.6:
> 
> commit f43d728731c691772ddc29e50d25c68a859935b5
> Author: Thomas Renninger <trenn@suse.de>
> Date:   Fri Aug 1 17:37:55 2008 +0200
> 
>     Check for ACPI backlight support otherwise use vendor ACPI drivers
> 
> 
> commit ad9ed8385ed6ec5be8da7094db911c824258ceec
> Author: Thomas Renninger <trenn@suse.de>
> Date:   Fri Aug 1 17:37:54 2008 +0200
> 
>     ACPI: video: Ignore devices that aren't present in hardware
> 
> I have been waiting for in-tree inclusion to submit patches for
> toshiba_acpi against stable base.

Ah, the commit id's above solved the mystery.
It looks like andi checked these patches directly into his
"test" branch rather than a topic branch.  eg. they were
sitting on top of the old pcc_acpi driver etc.

So I lost them when I deleted the old test branch
in order to merge the updated topic branches
into a new test branch.

-Len


  parent reply	other threads:[~2008-11-08  3:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-06  7:08 ACPI video.c brightness handler conflicts with toshiba_acpi Andrey Borzenkov
2008-09-06  7:19 ` Andrey Borzenkov
2008-09-08  1:01   ` Thomas Renninger
2008-09-08 17:24     ` Andrey Borzenkov
2008-10-27 16:52     ` Andrey Borzenkov
2008-10-28 13:26       ` Thomas Renninger
2008-10-28 15:15         ` Rafael J. Wysocki
2008-10-28 16:22           ` Andrey Borzenkov
2008-10-29 15:54             ` Thomas Renninger
2008-10-29 16:22               ` Andrey Borzenkov
2008-10-29 17:13               ` Andi Kleen
2008-10-29 21:01                 ` Thomas Renninger
2008-11-08  3:29             ` Len Brown [this message]
2008-10-28 18:08           ` Thomas Renninger
2008-09-08  1:13 ` Zhang Rui

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=alpine.LFD.2.00.0811072224200.9051@localhost.localdomain \
    --to=lenb@kernel.org \
    --cc=arvidjaar@mail.ru \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=toshiba_acpi@memebeam.org \
    --cc=trenn@suse.de \
    /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).