From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 111241] one need root credentials to read cpuinfo_cur_freq content
Date: Sun, 24 Jan 2016 17:09:14 +0000 [thread overview]
Message-ID: <bug-111241-137361-lET3BGTgtP@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-111241-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=111241
--- Comment #2 from flux242@gmail.com ---
well, the problem is 12 years people are still confused why it is this way.
Which makes me to believe that something is wrong with the design. Anyway, as
far as I can read from scaling_cur_freq I'm fine.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2016-01-24 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-24 9:16 [Bug 111241] New: one need root credentials to read cpuinfo_cur_freq content bugzilla-daemon
2016-01-24 16:33 ` [Bug 111241] " bugzilla-daemon
2016-01-24 17:09 ` bugzilla-daemon [this message]
2016-01-24 17:09 ` bugzilla-daemon
2016-05-16 21:47 ` 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-111241-137361-lET3BGTgtP@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-pm@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).