From: Thomas Gleixner <tglx@linutronix.de>
To: "Sébastien Dugué" <sebastien.dugue@bull.net>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.17-rc6-rt3
Date: Mon, 12 Jun 2006 11:21:58 +0200 [thread overview]
Message-ID: <1150104118.5257.219.camel@localhost.localdomain> (raw)
In-Reply-To: <1150104040.3835.3.camel@frecb000686>
On Mon, 2006-06-12 at 11:20 +0200, Sébastien Dugué wrote:
> >
> > I think all of the regressions reported against rt1 are fixed, please
> > re-report if any of them is still unfixed.
> >
>
> Great, boots fine on my dual Xeon and solves the ping problem I was
> having.
>
> Thomas, any hint at what was going on?
I missed some modificatons in the networking code when I did the forward
to 2.6.17-rc6. The network softirq was raised, but the thread not woken
up.
tglx
next prev parent reply other threads:[~2006-06-12 9:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-10 8:24 2.6.17-rc6-rt3 Ingo Molnar
2006-06-10 10:32 ` 2.6.17-rc6-rt3 Michal Piotrowski
2006-06-10 12:44 ` 2.6.17-rc6-rt3 Thomas Gleixner
2006-06-10 13:30 ` 2.6.17-rc6-rt3 Michal Piotrowski
2006-06-10 14:43 ` 2.6.17-rc6-rt3 Michal Piotrowski
2006-06-10 12:32 ` 2.6.17-rc6-rt3 Mike Galbraith
2006-06-11 12:38 ` 2.6.17-rc6-rt3 Mike Galbraith
2006-06-11 17:22 ` 2.6.17-rc6-rt3 Thomas Gleixner
2006-06-11 19:26 ` 2.6.17-rc6-rt3 Mark Knecht
2006-06-12 9:20 ` 2.6.17-rc6-rt3 Sébastien Dugué
2006-06-12 9:20 ` 2.6.17-rc6-rt3 Ingo Molnar
2006-06-12 9:35 ` 2.6.17-rc6-rt3 Sébastien Dugué
2006-06-12 9:21 ` Thomas Gleixner [this message]
2006-06-12 17:08 ` 2.6.17-rc6-rt3 K.R. Foley
2006-06-12 17:19 ` 2.6.17-rc6-rt3 K.R. Foley
2006-06-12 17:22 ` 2.6.17-rc6-rt3 Thomas Gleixner
2006-06-12 17:32 ` 2.6.17-rc6-rt3 K.R. Foley
2006-06-16 18:51 ` 2.6.17-rc6-rt3 Bruce Eleniak
2006-06-16 19:04 ` 2.6.17-rc6-rt3 Bruce Eleniak
2006-06-16 19:24 ` 2.6.17-rc6-rt3 K.R. Foley
-- strict thread matches above, loose matches on Subject: below --
2006-06-10 13:44 2.6.17-rc6-rt3 henry kay
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=1150104118.5257.219.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sebastien.dugue@bull.net \
/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