From: David Miller <davem@davemloft.net>
To: risto.suominen@gmail.com
Cc: khc@pm.waw.pl, netdev@vger.kernel.org
Subject: Re: [PATCH 002/002] de2104x: support for systems lacking cache coherence
Date: Wed, 11 Feb 2009 13:39:55 -0800 (PST) [thread overview]
Message-ID: <20090211.133955.60089579.davem@davemloft.net> (raw)
In-Reply-To: <46e1c7760902110431p54c0b5f7oa1a07726f4db5021@mail.gmail.com>
From: Risto Suominen <risto.suominen@gmail.com>
Date: Wed, 11 Feb 2009 14:31:43 +0200
> As an interesting side effect, the patch caused my mesh module to stop
> working. It crashes.
I think you need to take this discussion to linuxppc-dev at this
point.
Nobody amongst the networking developers can say whether
your NOT_COHERENT_CACHE change is a valid or desirable
way to solve the problem, nor what side effects it might
have.
next prev parent reply other threads:[~2009-02-11 21:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-07 21:30 [PATCH 002/002] de2104x: support for systems lacking cache coherence Risto Suominen
2009-02-09 7:27 ` Fwd: " Risto Suominen
2009-02-09 7:45 ` David Miller
2009-02-09 8:22 ` Risto Suominen
2009-02-09 8:29 ` David Miller
2009-02-09 8:35 ` Risto Suominen
2009-02-09 16:58 ` Krzysztof Halasa
2009-02-09 19:22 ` Risto Suominen
2009-02-09 22:51 ` David Miller
2009-02-10 1:45 ` Krzysztof Halasa
2009-02-10 1:50 ` David Miller
2009-02-10 23:21 ` David Miller
2009-02-11 12:18 ` Risto Suominen
2009-02-11 12:31 ` Risto Suominen
2009-02-11 21:39 ` David Miller [this message]
2009-02-13 3:42 ` Benjamin Herrenschmidt
2009-02-10 1:01 ` Andrew Morton
2009-02-10 1:07 ` David Miller
2009-02-10 7:16 ` Risto Suominen
2009-02-10 7:16 ` Risto Suominen
-- strict thread matches above, loose matches on Subject: below --
2009-02-12 11:22 Risto Suominen
2009-02-13 3:25 ` Benjamin Herrenschmidt
2009-02-13 3:26 ` Benjamin Herrenschmidt
2009-02-13 15:58 ` Risto Suominen
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=20090211.133955.60089579.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=khc@pm.waw.pl \
--cc=netdev@vger.kernel.org \
--cc=risto.suominen@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.