Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #59296
| From | owner@bugs.debian.org (Debian Bug Tracking System) |
|---|---|
| Newsgroups | linux.debian.kernel |
| Subject | Bug#880203: marked as done (After suspend&resume, cpufreq/scaling_max_freq is ignored) |
| Date | 2017-10-31 11:40 +0100 |
| Message-ID | <uGC7E-174-15@gated-at.bofh.it> (permalink) |
| References | <uGC7E-174-17@gated-at.bofh.it> <uGjHJ-6Nr-33@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
Your message dated Tue, 31 Oct 2017 10:36:59 +0000 with message-id <1509446219.2748.35.camel@decadent.org.uk> and subject line Re: Fwd: Re: Bug#880203: After suspend&resume, cpufreq/scaling_max_freq is ignored has caused the Debian Bug report #880203, regarding After suspend&resume, cpufreq/scaling_max_freq is ignored to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 880203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880203 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bug#880203: After suspend&resume, cpufreq/scaling_max_freq is ignored Leon Meier <Leon.Meier@yandex.ru> - 2017-10-30 16:00 +0100
Processed: Re: Bug#880203: After suspend&resume, cpufreq/scaling_max_freq is ignored owner@bugs.debian.org (Debian Bug Tracking System) - 2017-10-31 01:30 +0100
Bug#880203: After suspend&resume, cpufreq/scaling_max_freq is ignored Ben Hutchings <ben@decadent.org.uk> - 2017-10-31 01:30 +0100
Bug#880203: After suspend&resume, cpufreq/scaling_max_freq is ignored Leon Meier <Leon.Meier@yandex.ru> - 2017-10-31 11:20 +0100
Bug#880203: marked as done (After suspend&resume, cpufreq/scaling_max_freq is ignored) owner@bugs.debian.org (Debian Bug Tracking System) - 2017-10-31 11:40 +0100
Bug#880203: closed by Ben Hutchings <ben@decadent.org.uk> (Re: Fwd: Re: Bug#880203: After suspend&resume, cpufreq/scaling_max_freq is ignored) Leon Meier <Leon.Meier@yandex.ru> - 2017-10-31 13:40 +0100
Bug#880203: After suspend&resume, cpufreq/scaling_max_freq is ignored - (wild hack) shell script Leon Meier <Leon.Meier@yandex.ru> - 2017-11-01 13:20 +0100
Bug#880203: After suspend&resume, cpufreq/scaling_max_freq is ignored - (wild hack) shell script Ben Hutchings <ben@decadent.org.uk> - 2017-11-01 13:50 +0100
Bug#880203: closed by Ben Hutchings <ben@decadent.org.uk> (Re: Fwd: Re: Bug#880203: After suspend&resume, cpufreq/scaling_max_freq is ignored) Ben Hutchings <ben@decadent.org.uk> - 2017-11-01 13:50 +0100
Bug#880203: closed by Ben Hutchings <ben@decadent.org.uk> (Re: Fwd: Re: Bug#880203: After suspend&resume, cpufreq/scaling_max_freq is ignored) Leon Meier <Leon.Meier@yandex.ru> - 2017-11-01 14:00 +0100
Bug#880203: After suspend&resume, cpufreq/scaling_max_freq is ignored - alternative shell script Leon Meier <Leon.Meier@yandex.ru> - 2017-11-01 14:40 +0100
csiph-web