linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Olaf Hering <olh@suse.de>
Cc: Kaoru Fukui <k_fukui@highway.ne.jp>, linuxppc-dev@lists.linuxppc.org
Subject: Re: Kernel-2.4.7.pre5
Date: Tue, 10 Jul 2001 08:29:21 -0400	[thread overview]
Message-ID: <3B4AF521.45E57FAD@mandrakesoft.com> (raw)
In-Reply-To: 20010710142113.B21458@suse.de


Olaf Hering wrote:
>
> On Tue, Jul 10, Kaoru Fukui wrote:
>
> >
> > Hi!
> >
> > I had this problem in linuxppc_2_4 bk tree's linux-2.4.7.pre5.
> > Is my fix correct ?
>
> The "correct" fix would be somthing like that:
> /mirror/kernel/people/andrea/kernels/v2.4/2.4.7pre3aa1/00_ksoftirqd-7_ppc-2
>
> But Paul was/is not very happy about that softirq thing...

*shrug*   linux-2.4.7-pre5 softirqs should finally (a) have a coherent
implementation with no special cases, and (b) sort through all the bugs
and API weirdness that Ingo added in 2.4.6-preXX.

So Paul can be not happy but Linus is happy with the API, which is the
more important thing...

--
Jeff Garzik      | A recent study has shown that too much soup
Building 1024    | can cause malaise in laboratory mice.
MandrakeSoft     |

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-07-10 12:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-10 12:00 Kernel-2.4.7.pre5 Kaoru Fukui
2001-07-10 12:21 ` Kernel-2.4.7.pre5 Olaf Hering
2001-07-10 12:29   ` Jeff Garzik [this message]
2001-07-12  9:23     ` Kernel-2.4.7.pre5 Paul Mackerras
2001-07-10 17:44   ` Kernel-2.4.7.pre5 Tom Rini
2001-07-10 17:47     ` Kernel-2.4.7.pre5 Olaf Hering

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=3B4AF521.45E57FAD@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=k_fukui@highway.ne.jp \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=olh@suse.de \
    /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).