linux-kernel - cpufreq pull request.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20110614000715.GA3018@redhat.com>
Date:	Mon, 13 Jun 2011 20:07:15 -0400
From:	Dave Jones <davej@...hat.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: cpufreq pull request.

Please pull from ..
master.kernel.org:/pub/scm/linux/kernel/git/davej/cpufreq.git/ fixes

 MAINTAINERS                     |    1 -
 drivers/cpufreq/cpufreq_stats.c |    1 +
 2 files changed, 1 insertions(+), 1 deletions(-)

commit 13f067537f34456443f61c950cd6dc37d1d5f3ee
Author: Dave Jones <davej@...hat.com>
Date:   Sun Jun 12 16:35:28 2011 -0400

    [CPUFREQ] Remove cpufreq_stats sysfs entries on module unload.
    
    cpufreq_stats leaves behind its sysfs entries, which causes a panic
    when something stumbled across them.
    (Discovered by unloading cpufreq_stats while powertop was loaded).
    
    Signed-off-by: Dave Jones <davej@...hat.com>
    Cc: stable@...nel.org

commit 89b882a25e703b72c3e84c582357e3e864d8ccca
Author: Joe Perches <joe@...ches.com>
Date:   Wed Jun 1 10:59:10 2011 -0700

    MAINTAINERS: Update CPU FREQUENCY patterns
    
    Commit bb0a56ecc4ba ("[CPUFREQ] Move x86 drivers to drivers/cpufreq/")
    moved the files, remove the old pattern.
    
    Signed-off-by: Joe Perches <joe@...ches.com>
    Signed-off-by: Dave Jones <davej@...hat.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/