From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Andrew Morton <akpm@osdl.org>
Cc: Bradley Chapman <kakadu_croc@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test7-mm1
Date: Fri, 17 Oct 2003 10:15:41 +0100 [thread overview]
Message-ID: <20031017101541.A24238@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20031017002529.21528bc7.akpm@osdl.org>; from akpm@osdl.org on Fri, Oct 17, 2003 at 12:25:29AM -0700
On Fri, Oct 17, 2003 at 12:25:29AM -0700, Andrew Morton wrote:
> It's not an oops, it's a warning. cpufreq_register_notifier() is being
> called super-early but is taking a semaphore. I've asked the cpufreq guys
> if this can be moved to an initcall but received one of those stupid "your
> message is awaiting moderator approval" replies from the mailing list. I
> gave up at that point.
Not silly. Your message was oversize - at least you got something back
rather than it being blackholed like lkml does.
I forwarded it on to the list (after cutting out that massive 47K .config
file that was attached), but no one seems to be listening or interested
there.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2003-10-17 9:15 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031016083124.45a171a5.akpm@osdl.org>
2003-10-17 7:03 ` 2.6.0-test7-mm1 Bradley Chapman
2003-10-17 7:25 ` 2.6.0-test7-mm1 Andrew Morton
2003-10-17 9:15 ` Russell King [this message]
2003-10-16 14:44 2.6.0-test7-mm1 Steven Pratt
2003-10-16 14:58 ` 2.6.0-test7-mm1 Andrew Morton
2003-10-16 23:13 ` 2.6.0-test7-mm1 Steven Pratt
2003-10-17 7:23 ` 2.6.0-test7-mm1 Kirill Korotaev
2003-10-16 14:58 ` 2.6.0-test7-mm1 William Lee Irwin III
2003-10-19 14:16 ` 2.6.0-test7-mm1 Alexander Hoogerhuis
-- strict thread matches above, loose matches on Subject: below --
2003-10-15 12:17 2.6.0-test7-mm1 Jan Killius
2003-10-15 10:11 2.6.0-test7-mm1 Bradley Chapman
2003-10-15 10:22 ` 2.6.0-test7-mm1 Andrew Morton
2003-10-15 12:34 ` 2.6.0-test7-mm1 Bradley Chapman
2003-10-15 12:46 ` 2.6.0-test7-mm1 Tim Schmielau
2003-10-15 12:53 ` 2.6.0-test7-mm1 Bradley Chapman
2003-10-15 17:28 ` 2.6.0-test7-mm1 Andrew Morton
2003-10-15 17:40 ` 2.6.0-test7-mm1 Ben Collins
2003-10-15 17:53 ` 2.6.0-test7-mm1 Andrew Morton
2003-10-16 2:25 ` 2.6.0-test7-mm1 Ben Collins
2003-10-16 14:04 ` 2.6.0-test7-mm1 Anton Blanchard
2003-10-18 12:39 ` 2.6.0-test7-mm1 Kristian Høgsberg
2003-10-18 13:27 ` 2.6.0-test7-mm1 Ben Collins
2003-10-15 21:14 ` 2.6.0-test7-mm1 Alexander Hoogerhuis
2003-10-15 21:44 ` 2.6.0-test7-mm1 Andrew Morton
2003-10-15 8:36 2.6.0-test7-mm1 Andrew Morton
2003-10-15 15:20 ` 2.6.0-test7-mm1 Luiz Capitulino
2003-10-15 15:42 ` 2.6.0-test7-mm1 Luiz Capitulino
2003-10-15 16:55 ` 2.6.0-test7-mm1 William Lee Irwin III
2003-10-15 21:40 ` 2.6.0-test7-mm1 William Lee Irwin III
2003-10-16 15:11 ` 2.6.0-test7-mm1 Luiz Capitulino
2003-10-17 8:58 ` 2.6.0-test7-mm1 Kirill Korotaev
2003-10-17 9:10 ` 2.6.0-test7-mm1 William Lee Irwin III
2003-10-17 12:02 ` 2.6.0-test7-mm1 Luiz Capitulino
2003-10-18 17:43 ` 2.6.0-test7-mm1 Thomas Schlichter
2003-10-18 17:50 ` 2.6.0-test7-mm1 Andrew Morton
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=20031017101541.A24238@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=kakadu_croc@yahoo.com \
--cc=linux-kernel@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).