All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Neuer <mr.fred.smoothie@gmail.com>
To: Joe Peterson <joe@skyrush.com>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
	linux-input@atrey.karlin.mff.cuni.cz,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] to drivers/input/evdev.c to add mixer device "/dev/input/events"
Date: Mon, 15 Aug 2005 16:06:04 -0400	[thread overview]
Message-ID: <161717d505081513066c660129@mail.gmail.com> (raw)
In-Reply-To: <4300EF7C.9020500@skyrush.com>

On 8/15/05, Joe Peterson <joe@skyrush.com> wrote:
> 
> So, overall, I agree that we should not invent hacks to make up for
> another software package's problems...

but also wrote:

> If the kernel could handle that aspect, it would make all programs more stable.

which seems a little contradictory.

However, Joe continued with:

> It does not sound right to push the handling of the intermittent nature
> to each user program.

Indeed. Each user program should not care about it. An event/hotplug
library should, and the user programs should use that. Like d-bus/HAL.

Dave

  reply	other threads:[~2005-08-15 20:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15 17:27 [PATCH] to drivers/input/evdev.c to add mixer device "/dev/input/events" Joe Peterson
2005-08-15 17:45 ` Vojtech Pavlik
2005-08-15 18:00   ` Joe Peterson
2005-08-15 18:57     ` Vojtech Pavlik
2005-08-15 19:39       ` Joe Peterson
2005-08-15 20:06         ` Dave Neuer [this message]
2005-08-15 20:13           ` Vojtech Pavlik
2005-08-15 20:23           ` Joe Peterson
2005-08-16  8:38             ` Helge Hafting
2005-08-15 20:24         ` Jon Smirl
2005-08-15 21:05           ` Jon Smirl

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=161717d505081513066c660129@mail.gmail.com \
    --to=mr.fred.smoothie@gmail.com \
    --cc=joe@skyrush.com \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mr.fred.smoothie@pobox.com \
    --cc=vojtech@suse.cz \
    /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.