public inbox for cpufreq@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
	bugzilla-daemon@bugzilla.kernel.org,
	Andre Przywara <andre.przywara@linaro.org>,
	1i5t5.duncan@cox.net, cpufreq@vger.kernel.org,
	Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
	Thomas Renninger <trenn@suse.de>
Subject: Re: More cpufreq breakage
Date: Fri, 22 Mar 2013 16:13:48 +0100	[thread overview]
Message-ID: <20130322151348.GI30807@pd.tnic> (raw)
In-Reply-To: <20130322151228.GH30807@pd.tnic>

On Fri, Mar 22, 2013 at 04:12:28PM +0100, Borislav Petkov wrote:
> Btw,
> 
> while we're at it, I just discovered this in dmesg. Plain -rc3.

Forgot to say, this happened once during resume.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2013-03-22 15:13 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-55411-70601@https.bugzilla.kernel.org/>
     [not found] ` <20130319074953.C200811FB80@bugzilla.kernel.org>
2013-03-19  8:50   ` [Bug 55411] sysfs per-cpu cpufreq subdirs/symlinks screwed up after s2ram Viresh Kumar
2013-03-22 12:17     ` Rafael J. Wysocki
2013-03-22 12:15       ` Viresh Kumar
2013-03-22 13:12         ` Rafael J. Wysocki
2013-03-22 13:21           ` Borislav Petkov
2013-03-22 12:53       ` Thomas Renninger
2013-03-22 13:43         ` Viresh Kumar
2013-03-22 13:54           ` Borislav Petkov
2013-03-22 14:05             ` Viresh Kumar
2013-03-22 14:11               ` Borislav Petkov
2013-03-22 14:04           ` Thomas Renninger
2013-03-22 14:10             ` Viresh Kumar
2013-03-22 14:13               ` Borislav Petkov
2013-03-24  9:05             ` Thomas Renninger
2013-03-24  9:10               ` Viresh Kumar
2013-03-24 10:02                 ` Viresh Kumar
2013-03-24 11:49                   ` Duncan
2013-03-24 12:16                     ` Viresh Kumar
2013-03-24 12:23                       ` Viresh Kumar
2013-03-25 11:15                         ` Duncan
2013-03-25 11:23                           ` Viresh Kumar
2013-03-25 13:55                             ` Borislav Petkov
2013-03-29 14:14                             ` Viresh Kumar
2013-03-24 10:31                 ` Borislav Petkov
2013-03-22 15:12       ` More cpufreq breakage Borislav Petkov
2013-03-22 15:13         ` Borislav Petkov [this message]
2013-03-22 16:22         ` Viresh Kumar
2013-03-22 16:27           ` Viresh Kumar
2013-03-23 13:45           ` Borislav Petkov
2013-03-23 14:27             ` Rafael J. Wysocki
2013-03-23 14:34               ` Viresh Kumar
2013-03-23 15:16                 ` Viresh Kumar
2013-03-23 16:06                   ` Borislav Petkov
2013-03-23 17:04                     ` Viresh Kumar
2013-03-23 18:50                       ` Borislav Petkov
2013-03-24  9:05                         ` Viresh Kumar
2013-03-24 10:35                           ` Borislav Petkov
2013-03-23 18:35     ` [Bug 55411] sysfs per-cpu cpufreq subdirs/symlinks screwed up after s2ram Viresh Kumar

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=20130322151348.GI30807@pd.tnic \
    --to=bp@alien8.de \
    --cc=1i5t5.duncan@cox.net \
    --cc=andre.przywara@linaro.org \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=cpufreq@vger.kernel.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=rjw@sisk.pl \
    --cc=trenn@suse.de \
    --cc=viresh.kumar@linaro.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