All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann Cantin <yann.cantin@laposte.net>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, linux-usb@vger.kernel.org,
	gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC ebeam PATCH 3/3] input: misc: New USB eBeam input driver.
Date: Mon, 30 Jul 2012 16:25:00 +0200	[thread overview]
Message-ID: <5016993C.9010906@laposte.net> (raw)
In-Reply-To: <20120730055623.GD5830@core.coreip.homeip.net>

Hi,

>> The code structure (device selector + functions indirection) also seems overkill
>> to me for now, but permit to anticipate device's variations. If it appears that they
>> all works in the same way, it'll be easy (and more comfortable to me) to step down,
>> the opposite seems more difficult.
> 
> Actually I am hesitant to add infrastructure if it is unclear if we need
> it at all.

Understand.

I've thrown some hook to see if i can get my hands on other devices.

In the meantime, i'll bet on uniform support and strip down the driver. Wish me luck.

Thanks.
-- 
Yann Cantin
A4FEB47F
--

      reply	other threads:[~2012-07-30 14:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-28  0:02 [RFC ebeam PATCH 0/3] new USB eBeam input driver Yann Cantin
2012-07-28  0:02 ` [RFC ebeam PATCH 1/3] hid: hid-ids.h: Add vendor and device ID for eBeam classic device Yann Cantin
2012-07-28  0:02 ` [RFC ebeam PATCH 2/3] hid: hid-core.c: Blackist " Yann Cantin
     [not found] ` <1343433754-3887-1-git-send-email-yann.cantin-QFKgK+z4sOrR7s880joybQ@public.gmane.org>
2012-07-28  0:02   ` [RFC ebeam PATCH 3/3] input: misc: New USB eBeam input driver Yann Cantin
2012-07-28  0:02     ` Yann Cantin
2012-07-28  1:42     ` Dmitry Torokhov
2012-07-28  9:02       ` Yann Cantin
2012-07-30  5:56         ` Dmitry Torokhov
2012-07-30 14:25           ` Yann Cantin [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=5016993C.9010906@laposte.net \
    --to=yann.cantin@laposte.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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.