public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Jason Vas Dias <jason.vas.dias@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Matthew Garrett <mjg@redhat.com>, Len Brown <len.brown@intel.com>,
	Comrade DOS <suloevdmitry@gmail.com>,
	linux-kernel@vger.kernel.org,
	Andreas Herrmann <andreas.herrmann3@amd.com>
Subject: Re: PROBLEM: Performance drop
Date: Thu, 27 Sep 2012 19:48:24 +0200	[thread overview]
Message-ID: <20120927174824.GD8759@x1.osrc.amd.com> (raw)
In-Reply-To: <20120927173456.GA21025@kroah.com>

On Thu, Sep 27, 2012 at 10:34:56AM -0700, Greg Kroah-Hartman wrote:
> On Sat, Jul 14, 2012 at 12:11:41PM +0100, Jason Vas Dias wrote:
> > Hi - any progress on this or on the patch I submitted for it ? -
> > please see enclosed - apologies for my being forced to use gmail which
> > has mandatory line wrap -
> > Please do something about restoring correct thermal operation on
> > x86_64 K8's with HP BIOS !
> > Thanks & Regards,
> > Jason
> > 
> > Re: [PATCH: 1/1] ACPI: make evaluation of thermal trip points before
> > temperature or vice versa dependant on new "temp_b4_trip" module
> > parameter to support older AMD x86_64s
> 
> I don't see this patch in Linus's tree, so I can't do anything about it
> in a stable kernel release.  Please work with the ACPI developers to get
> it pushed to Linus's tree, and after that, let me know what the git
> commit id is of it so I can add it to a stable release.

Yeah,

this patch adds a dmi quirk *and* a module parameter which looks kinda
too much to me. In any case, Andreas needs to look at this since he's
been dealing with those old laptops.

Jason, can you clean up your patch, drop the module parameter, write a
proper commit message, run it through checkpatch.pl and send it as a
reply to this thread with a mail client which doesn't mangle it so that
we can look at it further?

Thanks.

-- 
Regards/Gruss,
Boris.

  reply	other threads:[~2012-09-27 17:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-23 19:12 PROBLEM: Performance drop Comrade DOS
2012-05-24 12:31 ` Andreas Herrmann
     [not found]   ` <CA+fU7qfPznJpRABC4Z=xmRZW6p5Mw3dFLBySk9HuPnaCYMMnEg@mail.gmail.com>
2012-05-26  6:11     ` Comrade DOS
     [not found]     ` <20120529140940.GA10421@alberich.amd.com>
2012-05-29 20:20       ` Comrade DOS
2012-05-30 12:43         ` Andreas Herrmann
     [not found]           ` <CA+fU7qehx6Jjb0ZWNrh+bh6SYCKLVWZDd7iLnsC=hDVqqFd74Q@mail.gmail.com>
2012-07-06  2:47             ` Fwd: " Comrade DOS
2012-07-07 14:40           ` Jason Vas Dias
2012-07-07 14:45             ` Jason Vas Dias
2012-07-11 22:06             ` Greg Kroah-Hartman
2012-07-14 11:11               ` Jason Vas Dias
2012-09-27 17:34                 ` Greg Kroah-Hartman
2012-09-27 17:48                   ` Borislav Petkov [this message]
2012-10-09 22:19                     ` katabami
2012-10-18  1:21                     ` katabami

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=20120927174824.GD8759@x1.osrc.amd.com \
    --to=bp@alien8.de \
    --cc=andreas.herrmann3@amd.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jason.vas.dias@gmail.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg@redhat.com \
    --cc=suloevdmitry@gmail.com \
    /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