mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Arthur Machlas <arthur.machlas@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reconsider including phc-linux patch to control voltages
Date: Tue, 17 May 2011 07:46:29 -0700	[thread overview]
Message-ID: <20110517144629.GC25545@kroah.com> (raw)
In-Reply-To: <BANLkTikn3OawHFO8y20sLuK_4LxOw7nQBg@mail.gmail.com>

On Tue, May 17, 2011 at 09:39:23AM -0500, Arthur Machlas wrote:
> Hi, please cc me on any replies.
> 
> Five years ago a request was made[1] to include some patches from the
> phc-linux project. This request was rejected for reasons of stability,
> wasting dev time chasing bugs, and general discomfort. Mildly
> supportive suggestions were made to make it either a separate driver
> (it patches acpi-cpufreq) or call some 'tainted' flags.
> 
> It is currently included in the zen kernel, and now supports out of
> tree building making it somewhat unecessary to include, however, the
> dev's seem unable to keep up with newer kernels and releases are
> becoming infrequent. Users now seem to be modifying the patch to make
> sure it cleanly applies to newer kernels. Gentoo seems to be doing
> this at the distro level [2].
> 
> Just wondering if any circumstances have changed that would merit
> reconsidering the decision to not include the patches.
> 
> Many thanks,
> Arthur
> 
> [1] http://lkml.org/lkml/2007/9/2/119
> [2] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-power/phc-intel/files/phc-intel-0.3.2.12.1-2.6.38.patch?view=markup


Why not submit it to the acpi developers in the proper format (i.e. what
Documentation/SubmittingPatches describes) and see how it goes?

thanks,

greg k-h

      reply	other threads:[~2011-05-17 14:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17 14:39 Arthur Machlas
2011-05-17 14:46 ` Greg KH [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=20110517144629.GC25545@kroah.com \
    --to=greg@kroah.com \
    --cc=arthur.machlas@gmail.com \
    --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

Powered by JetHome