From: Con Kolivas <kernel@kolivas.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: rt-preempt build failure
Date: Thu, 7 Jul 2005 00:33:03 +1000 [thread overview]
Message-ID: <200507070033.03948.kernel@kolivas.org> (raw)
In-Reply-To: <20050706134950.GC19467@elte.hu>
On Wed, 6 Jul 2005 23:49, Ingo Molnar wrote:
> * Con Kolivas <kernel@kolivas.org> wrote:
> > > thanks, i have fixed this and have uploaded the -51-00 patch.
> >
> > Thanks. boots and runs stable after a swag of these initially
> > (?netconsole related):
> ok, the patch below (or -51-04 and later kernels) should fix this one.
> printk is fully preemptible from now on - lets see how it works out in
> practice. (i kept it under irqs-off to make sure we get all crash
> messages out. Perhaps we could disable irqs/preemption if
> oops_in_progress?) This patch should also fix similar, fbcon related
> messages.
Works fine, thanks!
Con
prev parent reply other threads:[~2005-07-06 19:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-05 13:08 rt-preempt build failure Con Kolivas
2005-07-05 13:51 ` Ingo Molnar
2005-07-06 13:03 ` Con Kolivas
2005-07-06 13:49 ` Ingo Molnar
2005-07-06 14:33 ` Con Kolivas [this message]
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=200507070033.03948.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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