From: Greg KH <gregkh@suse.de>
To: Len Brown <lenb@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Hiroshi Miura <miura@da-cha.org>,
YOKOTA Hiroshi <yokota@netlab.is.tsukuba.ac.jp>,
Harald Welte <laforge@gnumonks.org>,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH 01/42] Staging: add pcc-acpi driver
Date: Wed, 22 Oct 2008 21:55:05 -0700 [thread overview]
Message-ID: <20081023045505.GA7539@suse.de> (raw)
In-Reply-To: <alpine.LFD.1.10.0810222244130.3010@localhost.localdomain>
On Wed, Oct 22, 2008 at 10:49:26PM -0400, Len Brown wrote:
>
>
> On Wed, 22 Oct 2008, Greg KH wrote:
>
> > On Wed, Oct 22, 2008 at 02:37:18PM -0400, Len Brown wrote:
> > > NAK.
> > > this was already relplaced by the panasonic driver in the acpi tree.
> >
> > Is this in 2.6.27, or was it a 2.6.28 addition? For some reason, I had
> > reports from openSUSE users that 2.6.27 still didn't work properly and
> > needed this driver.
> >
> > How about the new "pcc-acpi-cdrom" driver hack? Hiroshi, is that needed
> > still with the 2.6.27 kernel?
>
> drivers/misc/panasonic-laptop.c is staged for 2.6.28:
>
> http://git.kernel.org/?p=linux/kernel/git/lenb/linux-acpi-2.6.git;a=history;f=drivers/misc/panasonic-laptop.c;h=a2cb598d8ab54a98000d1f31f7c2407924399a5e;hb=test
Hm, we didn't get the acpi merge with Linus yet for .28? No wonder I
missed this, sorry about it.
> > > Greg,
> > > If it has the word "acpi" in it, please check with me before
> > > putting something in the staging tree, for I'd prefer to
> > > stage such things in the acpi tree.
> >
> > Ok, I didn't know you wanted "uncleaned" drivers in your tree, I'll
> > remember this for the future :)
>
> AFAICK, the driver that was checked into staging tree
> was based on an older version of the driver already staged
> in the acpi tree. I think that the staging tree
> isn't helping us in this scenario.
Fair enough, I'll drop it from my tree, thanks for paying attention and
letting me know.
greg k-h
next prev parent reply other threads:[~2008-10-23 5:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081022172203.GA4000@kroah.com>
[not found] ` <1224696563-5170-1-git-send-email-gregkh@suse.de>
[not found] ` <alpine.LFD.1.10.0810221434070.3010@localhost.localdomain>
[not found] ` <20081022184808.GA24150@suse.de>
2008-10-23 2:49 ` [PATCH 01/42] Staging: add pcc-acpi driver Len Brown
2008-10-23 4:55 ` Greg KH [this message]
2008-10-23 19:26 ` [GIT PATCH] delete pcc_acpi Len Brown
2008-10-23 20:22 ` Greg KH
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=20081023045505.GA7539@suse.de \
--to=gregkh@suse.de \
--cc=laforge@gnumonks.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miura@da-cha.org \
--cc=yokota@netlab.is.tsukuba.ac.jp \
/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