From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
"open list:STAGING SUBSYSTEM" <devel@driverdev.osuosl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: new asus fan driver
Date: Wed, 6 Nov 2013 14:30:59 +0000 [thread overview]
Message-ID: <20131106143059.GA24451@srcf.ucam.org> (raw)
In-Reply-To: <20131106085556.GA9487@kroah.com>
On Wed, Nov 06, 2013 at 12:55:56AM -0800, Greg Kroah-Hartman wrote:
> Matthew, please don't push drivers to the staging tree that have no
> problems on their own, and don't require work within them to get out of
> staging, as that doesn't help much, as I don't want to take code that
> has to wait for external things to happen before it can move out of
> staging.
I'm not willing to commit to supporting this code with the
virt_to_phys() hack in place, but I also don't want to block Felipe from
having an incentive to fix up the ACPI core so we can do this cleanly.
What I suggested was adding it to the asus-wmi driver and wrapping the
functionality with CONFIG_STAGING in order to indicate that there were
no promises that this feature would remain, and then giving Felipe a few
months to do the ACPI work. If it got done in a reasonable time then
we'd keep the code, and if not I'd drop it. I certainly didn't suggest
writing a separate driver, let alone putting it in staging.
--
Matthew Garrett | mjg59@srcf.ucam.org
prev parent reply other threads:[~2013-11-06 14:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 8:59 [PATCH] staging: new asus fan driver Felipe Contreras
2013-11-05 12:52 ` Greg Kroah-Hartman
2013-11-05 14:29 ` Felipe Contreras
2013-11-05 15:16 ` Greg Kroah-Hartman
2013-11-05 19:54 ` Felipe Contreras
2013-11-06 2:19 ` Greg Kroah-Hartman
2013-11-06 2:52 ` Felipe Contreras
2013-11-06 8:55 ` Greg Kroah-Hartman
2013-11-06 14:30 ` Matthew Garrett [this message]
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=20131106143059.GA24451@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=devel@driverdev.osuosl.org \
--cc=felipe.contreras@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.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