From: Hendrik Wiese <7.e.Q@syncro-community.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Davide Rossetti <davide.rossetti@roma1.infn.it>,
LKLM <linux-kernel@vger.kernel.org>
Subject: Re: Difference wait_event_interruptible and interruptible_wait_on
Date: Thu, 25 Nov 2004 09:37:31 +0100 [thread overview]
Message-ID: <41A599CB.9070800@syncro-community.de> (raw)
In-Reply-To: <1101306293.2811.18.camel@laptop.fenrus.org>
Arjan van de Ven wrote:
>On Wed, 2004-11-24 at 14:42 +0100, Hendrik Wiese wrote:
>
>
>
>>So what should such a condition be? What should be put there?
>>
>>
>
>depends on your code.. do you have an URL to your driver source so that
>people can see what you're asking ?
>
>
>
>
>
It is a proprietary driver developed for access to passive and active
modules inside a vme-rack. Active modules can communicate with each
other over an IP layer created by the driver on top of the VME
architecture (dual port ram, Tundra Universe II PCI-VME Bridge) and on
the other hand a device for communication between active and passive
modules. I don't know if I may make the source code public, 'cos it is
property of my employer. I have to communicate this. I know there is
something called GPL and I also know what it means, but I fear my
oppinion won't be heard by my employer. Well... it's worth a try.
prev parent reply other threads:[~2004-11-25 9:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 12:05 Difference wait_event_interruptible and interruptible_wait_on Hendrik Wiese
2004-11-24 13:30 ` Davide Rossetti
2004-11-24 13:42 ` Hendrik Wiese
2004-11-24 14:24 ` Arjan van de Ven
2004-11-25 8:37 ` Hendrik Wiese [this message]
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=41A599CB.9070800@syncro-community.de \
--to=7.e.q@syncro-community.de \
--cc=arjan@infradead.org \
--cc=davide.rossetti@roma1.infn.it \
--cc=linux-kernel@vger.kernel.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 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.