public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Momchil Velikov <velco@fadata.bg>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Tom Rini <trini@kernel.crashing.org>,
	<linux-kernel@vger.kernel.org>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [PATCH] mesh: target 0 aborted
Date: 02 Jan 2002 11:49:56 +0200	[thread overview]
Message-ID: <87g05pytdn.fsf@fadata.bg> (raw)
In-Reply-To: <20020101234546.GO28513@cpe-24-221-152-185.az.sprintbbd.net> <20020102091710.14178@smtp.noos.fr>
In-Reply-To: <20020102091710.14178@smtp.noos.fr>

>>>>> "Benjamin" == Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:

>>> 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.

Benjamin> The up to date mesh driver didn't get into 2.4.18pre1, either I forgot
Benjamin> to send it to Marcelo along with the other PPC patches, or he missed it.

Benjamin> I'll take care of this.

Benjamin> The other patch for getting rid of "target 0 aborted" need some more
Benjamin> review. You seem to just remove the bus reset. That could be made a
Benjamin> driver option in case it really cause trouble, but I suppose the bug
Benjamin> is elsewhere (while beeing triggered by the bus reset).

Benjamin> I'll look into this around next week.

Thanks a lot.

Regards,
-velco

  reply	other threads:[~2002-01-02  9:51 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
2002-01-02  9:49     ` Momchil Velikov [this message]
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=87g05pytdn.fsf@fadata.bg \
    --to=velco@fadata.bg \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=trini@kernel.crashing.org \
    /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