From: "Stefan Lippers-Hollmann" <s.L-H@gmx.de>
To: Greg KH <greg@kroah.com>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
len.brown@intel.com, stable@kernel.org, gregkh@suse.de,
linux-kernel@vger.kernel.org, ranma+kernel@tdiedrich.de
Subject: Re: [stable] patch thinkpad-acpi-fix-incorrect-use-of-tpacpi_brght_mode_ecnvram.patch added to 2.6.30-stable tree
Date: Fri, 14 Aug 2009 01:02:45 +0200 [thread overview]
Message-ID: <200908140102.47341.s.L-H@gmx.de> (raw)
In-Reply-To: <20090813222801.GA9102@kroah.com>
Hi
On Friday 14 August 2009, Greg KH wrote:
> On Thu, Aug 06, 2009 at 08:31:11PM -0300, Henrique de Moraes Holschuh wrote:
> > On Fri, 07 Aug 2009, Stefan Lippers-Hollmann wrote:
> > > This patch fails to compile if applied to 2.6.30 + current stable queue.
> > [...]
> > > It seems to depend on the new quirk handling, introduced in:
> > > commit 7d95a3d564901e88ed42810f054e579874151999
> >
> > Good catch. And I _will_ need that quirk handling stuff to keep 2.6.30 in
> > shape :-(
>
> Oops, sorry for missing this.
>
> > The dependencies for the "thinkpad-acpi: fix incorrect use of
> > TPACPI_BRGHT_MODE_ECNVRAM" patch are:
>
> Due to the need to add a new feature just to get these quirks to work,
> I'll just drop this single patch, which should keep everything building
> properly, right?
Yes, dropping this patch
thinkpad-acpi-fix-incorrect-use-of-tpacpi_brght_mode_ecnvram.patch
results in a buildable tree again.
> thanks,
>
> greg k-h
Regards
Stefan Lippers-Hollmann
next prev parent reply other threads:[~2009-08-13 23:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090805205011.57FB548DF1@coco.kroah.org>
2009-08-06 23:08 ` patch thinkpad-acpi-fix-incorrect-use-of-tpacpi_brght_mode_ecnvram.patch added to 2.6.30-stable tree Stefan Lippers-Hollmann
2009-08-06 23:31 ` Henrique de Moraes Holschuh
2009-08-13 22:28 ` [stable] " Greg KH
2009-08-13 23:02 ` Stefan Lippers-Hollmann [this message]
2009-08-13 23:32 ` Greg KH
2009-08-14 1:54 ` 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=200908140102.47341.s.L-H@gmx.de \
--to=s.l-h@gmx.de \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=hmh@hmh.eng.br \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ranma+kernel@tdiedrich.de \
--cc=stable@kernel.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