LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Philipp Beyer <philipp.beyer@alliedvisiontec.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux-kernel@vger.kernel.org, linux1394-devel@lists.sourceforge.net
Subject: Re: ieee1394 feature needed: overwrite SPLIT_TIMEOUT from userspace
Date: Mon, 15 Jan 2007 15:54:30 +0100	[thread overview]
Message-ID: <1168872870.5190.18.camel@ahr-pbe-lx.avtnet.local> (raw)
In-Reply-To: <45AB8A5E.7040006@s5r6.in-berlin.de>


> > I will now try to work around this problem in userspace basically by
> > ignoring the timeout error.
> 
> I.e. something similar but less sophisticated than the protocol 01...09?
> 

In fact steps 01-09 describe what I had in mind pretty well :-) 

  reply	other threads:[~2007-01-15 14:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-12 11:42 Philipp Beyer
2007-01-13 18:15 ` Stefan Richter
2007-01-15 13:21   ` Philipp Beyer
2007-01-15 14:06     ` Stefan Richter
2007-01-15 14:54       ` Philipp Beyer [this message]
2007-01-15 18:30         ` Stefan Richter
2007-01-15 18:54     ` Kristian Høgsberg

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=1168872870.5190.18.camel@ahr-pbe-lx.avtnet.local \
    --to=philipp.beyer@alliedvisiontec.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=stefanr@s5r6.in-berlin.de \
    --subject='Re: ieee1394 feature needed: overwrite SPLIT_TIMEOUT from userspace' \
    /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

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