From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Momchil Velikov <velco@fadata.bg>, Tom Rini <trini@kernel.crashing.org>
Cc: <linux-kernel@vger.kernel.org>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [PATCH] mesh: target 0 aborted
Date: Wed, 2 Jan 2002 10:17:10 +0100 [thread overview]
Message-ID: <20020102091710.14178@smtp.noos.fr> (raw)
In-Reply-To: <20020101234546.GO28513@cpe-24-221-152-185.az.sprintbbd.net>
In-Reply-To: <20020101234546.GO28513@cpe-24-221-152-185.az.sprintbbd.net>
>> This patch makes mesh.c compile, by adapting it to the new
>> pmac_feature API (ported from the ppc tree).
>>
>> In addition it contains the fix from Thomas Capricelli for the
>> infamous "mesh: target 0 aborted" error, which I've been personally
>> observing since 2.1.13x.
>
>Er, what exactly is this against? If this is just what's in the
>linuxppc_2_4 tree against current 2.4.18pre, this is either (or will be
>now :)) on BenH's list of things to resend to Marcelo, or there's a
>problem with it still. If you added in another patch, please re-send
>this vs the linuxppc_2_4 tree.
The up to date mesh driver didn't get into 2.4.18pre1, either I forgot
to send it to Marcelo along with the other PPC patches, or he missed it.
I'll take care of this.
The other patch for getting rid of "target 0 aborted" need some more
review. You seem to just remove the bus reset. That could be made a
driver option in case it really cause trouble, but I suppose the bug
is elsewhere (while beeing triggered by the bus reset).
I'll look into this around next week.
Ben.
next prev parent reply other threads:[~2002-01-02 9:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-01 22:45 [PATCH] mesh: target 0 aborted Momchil Velikov
2002-01-01 23:45 ` Tom Rini
2002-01-02 6:56 ` Momchil Velikov
2002-01-02 9:17 ` Benjamin Herrenschmidt [this message]
2002-01-02 9:49 ` Momchil Velikov
2002-01-02 11:17 ` Thomas Capricelli
2002-01-02 12:08 ` Benjamin Herrenschmidt
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=20020102091710.14178@smtp.noos.fr \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.org \
--cc=velco@fadata.bg \
/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.