From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 64271] Intel Pstate driver - "kick" code is not needed
Date: Mon, 04 Nov 2013 16:42:26 +0000 [thread overview]
Message-ID: <bug-64271-12968-bYZN77pbVB@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-64271-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=64271
--- Comment #3 from Doug Smythies <dsmythies@telus.net> ---
Dirk: I do not know how to submit a patch. Which doesn't mean I shouldn't learn
how, but I have also been cheating when I make my "no kick" test code by just
deleting the 3 lines that decide to and do the kick. The real solution would be
a bit more. I'll do it of you want (it would be a good way to get rid of me for
awhile (just joking)).
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2013-11-04 16:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 22:17 [Bug 64271] New: Intel Pstate driver - "kick" code is not needed bugzilla-daemon
2013-11-03 21:13 ` [Bug 64271] " bugzilla-daemon
2013-11-04 16:17 ` bugzilla-daemon
2013-11-04 16:42 ` bugzilla-daemon [this message]
2013-11-04 17:01 ` bugzilla-daemon
2013-11-05 23:12 ` bugzilla-daemon
2014-04-15 6:30 ` bugzilla-daemon
2014-04-15 6:30 ` bugzilla-daemon
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=bug-64271-12968-bYZN77pbVB@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=cpufreq@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;
as well as URLs for NNTP newsgroup(s).