All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux-scsi@vger.kernel.org, linux1394-devel@lists.sourceforge.net
Subject: Re: 100% repeatable way to send firewire out to lunch permanently on 2.6.8.1
Date: Sun, 31 Jul 2005 18:59:46 +0100	[thread overview]
Message-ID: <20050731175946.GA8511@infradead.org> (raw)
In-Reply-To: <42ED1073.7010004@s5r6.in-berlin.de>

On Sun, Jul 31, 2005 at 07:54:59PM +0200, Stefan Richter wrote:
> Well, the LLD can _try_ it, but it may go horribly wrong.

It seems to work nicely for everyone but sbp2..

  reply	other threads:[~2005-07-31 17:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0409050434540.8779-100000@sasami.anime.net>
2004-10-24 14:42 ` 100% repeatable way to send firewire out to lunch permanently on 2.6.8.1 Olaf Hering
2004-10-24 14:53   ` James Bottomley
2004-10-24 15:00     ` Olaf Hering
2004-10-24 15:22       ` James Bottomley
2004-10-24 17:22         ` Dmitry Torokhov
2004-10-24 18:02         ` Olaf Hering
2004-10-24 19:29         ` Olaf Hering
2005-07-31 14:43           ` Dan Hollis
2005-07-31 17:31             ` Stefan Richter
2005-07-31 17:54               ` Stefan Richter
2005-07-31 17:59                 ` Christoph Hellwig [this message]
2005-07-31 18:08                   ` Stefan Richter
2005-07-31 19:16             ` Olaf Hering
2005-07-31 22:57               ` [PATCH] ieee1394/sbp2: fix for hot-unplug Stefan Richter
2005-07-31 23:14               ` 100% repeatable way to send firewire out to lunch permanently on 2.6.8.1 Stefan Richter
2004-10-31 21:05   ` Herbert Schmid
     [not found] <200410241930.47104.chrivers@iversen-net.dk>
2004-10-24 18:12 ` Stefan Richter

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=20050731175946.GA8511@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=stefanr@s5r6.in-berlin.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 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.