From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 73781] acpi-cpufreq cannot be loaded.
Date: Thu, 10 Apr 2014 15:44:01 +0000 [thread overview]
Message-ID: <bug-73781-12968-tM7XqjnmRZ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-73781-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=73781
--- Comment #2 from KATO Hiroshi <katoh@mikage.ne.jp> ---
commit eb8c68ef558e6cba241e7ada54f6b3427cb2bf68
Author: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Date: Mon Jan 27 22:50:35 2014 -0500
I reverted this patch and built module. And it doesn't seem to make any
difference.
commit cfc9c8ed03e4d908f2388af8815f44c87b503aaf
Author: Lukasz Majewski <l.majewski@samsung.com>
Date: Fri Dec 20 15:24:50 2013 +0100
I can't revert this patch, because some rejects happened.
commit 6f19efc0a1ca08bc61841b971d8b85ab505d95c8
Author: Lukasz Majewski <l.majewski@samsung.com>
Date: Fri Dec 20 15:24:49 2013 +0100
While building modules, many errors occured. So I didn't test this.
I apologize for bothering you.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2014-04-10 15:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 14:23 [Bug 73781] New: acpi-cpufreq cannot be loaded bugzilla-daemon
2014-04-10 14:52 ` [Bug 73781] " bugzilla-daemon
2014-04-10 15:44 ` bugzilla-daemon [this message]
2014-04-11 3:40 ` bugzilla-daemon
2014-04-11 8:05 ` bugzilla-daemon
2014-04-11 12:44 ` bugzilla-daemon
2014-04-11 12:44 ` bugzilla-daemon
2014-04-11 12:46 ` bugzilla-daemon
2014-04-11 12:52 ` bugzilla-daemon
2014-04-11 14:07 ` bugzilla-daemon
2014-04-11 15:17 ` bugzilla-daemon
2014-04-16 8:57 ` bugzilla-daemon
2014-04-16 12:39 ` bugzilla-daemon
2014-04-17 8:13 ` bugzilla-daemon
2014-04-17 15:07 ` bugzilla-daemon
2014-04-17 15:24 ` bugzilla-daemon
2014-04-18 1:59 ` 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-73781-12968-tM7XqjnmRZ@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.