From: Greg KH <greg@kroah.com>
To: "Patrick J. LoPresti" <patl@users.sourceforge.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Load hid.o module synchronously?
Date: Tue, 4 May 2004 19:56:02 -0700 [thread overview]
Message-ID: <20040505025602.GA19873@kroah.com> (raw)
In-Reply-To: <s5gy8o7bnhv.fsf@patl=users.sf.net>
On Tue, May 04, 2004 at 10:49:56PM -0400, Patrick J. LoPresti wrote:
> Greg KH <greg@kroah.com> writes:
>
> > On Tue, May 04, 2004 at 05:56:48PM -0400, Patrick J. LoPresti wrote:
> >
> > > But what if it fails to bind? For example, what if an error occurs?
> > > Or what if the keyboard is on the module's blacklist? How do I know
> > > when to stop waiting?
> >
> > You do not, sorry.
>
> That is disappointing. I mean, I deal with Microsoft products a lot,
> where "unreliable by design" is normal. But I expected better from
> Linux.
That is such an obvious troll and flame bait, I really do not know why I
am responding. Please, try to be civil here. The point of Linux isis,
if you don't like the way things are today, you can change them. Try
that with Microsoft products (for that manner, please show me how you
can do what you are trying to do on Windows 2000, driver stuff there is
_so_ much more complex...)
But before you try to do that (which basically is moving things back to
the way things used to be years ago in 2.2), why don't you try to state
the problem you are having. Perhaps it can be solved in a different
manner than what you are trying to do.
So, what are you trying to fix/solve/monitor/do here?
thanks,
greg k-h
next prev parent reply other threads:[~2004-05-05 3:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 19:10 Load hid.o module synchronously? Patrick J. LoPresti
2004-04-26 19:40 ` Chris Friesen
2004-04-26 19:50 ` Patrick J. LoPresti
2004-04-26 20:03 ` Chris Friesen
2004-04-26 20:19 ` Greg KH
2004-04-28 14:02 ` Bill Davidsen
[not found] ` <mit.lcs.mail.linux-kernel/c6od9g$53k$1@gatekeeper.tmr.com>
2004-05-01 13:21 ` Patrick J. LoPresti
2004-05-01 16:43 ` Kevin P. Fleming
2004-05-04 20:01 ` Greg KH
2004-05-04 21:56 ` Patrick J. LoPresti
2004-05-04 22:35 ` Greg KH
2004-05-05 2:49 ` Patrick J. LoPresti
2004-05-05 2:56 ` Greg KH [this message]
2004-05-05 15:19 ` Patrick J. LoPresti
2004-05-05 22:45 ` Greg KH
2004-05-06 13:54 ` Patrick J. LoPresti
2004-05-07 22:00 ` Greg KH
2004-05-05 3:21 ` Randy.Dunlap
2004-05-05 22:33 ` Oliver Neukum
2004-05-06 14:05 ` Patrick J. LoPresti
2004-05-07 16:19 ` Stefan Smietanowski
2004-05-07 17:50 ` Oliver Neukum
2004-04-27 6:02 ` Kim Holviala
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=20040505025602.GA19873@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patl@users.sourceforge.net \
/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