All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann Cantin <yann.cantin@laposte.net>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-input@vger.kernel.org, linux-usb@vger.kernel.org,
	gregkh@linuxfoundation.org, dmitry.torokhov@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC ebeam PATCH v2 0/3] new USB eBeam input driver
Date: Fri, 03 Aug 2012 14:13:23 +0200	[thread overview]
Message-ID: <501BC063.9040502@laposte.net> (raw)
In-Reply-To: <alpine.LRH.2.00.1208021602250.15211@twin.jikos.cz>

Hi,

Le 02/08/2012 16:16, Jiri Kosina a écrit :
>> Patch 1 and 2 are here to let the ebeam driver be choose to handle
>> the device instead of the generic-usb hid one (totally useless).
> 
> Just merge 1 and 2 together, not necessary to have two commits because of 
> that.

Ok, will do that for the next iteration of the patchset (i don't think
i need to resubmit now with this change only, no?)

Thanks.
-- 
Yann Cantin
A4FEB47F
--
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Yann Cantin <yann.cantin@laposte.net>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-input@vger.kernel.org, linux-usb@vger.kernel.org,
	gregkh@linuxfoundation.org, dmitry.torokhov@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC ebeam PATCH v2 0/3] new USB eBeam input driver
Date: Fri, 03 Aug 2012 14:13:23 +0200	[thread overview]
Message-ID: <501BC063.9040502@laposte.net> (raw)
In-Reply-To: <alpine.LRH.2.00.1208021602250.15211@twin.jikos.cz>

Hi,

Le 02/08/2012 16:16, Jiri Kosina a écrit :
>> Patch 1 and 2 are here to let the ebeam driver be choose to handle
>> the device instead of the generic-usb hid one (totally useless).
> 
> Just merge 1 and 2 together, not necessary to have two commits because of 
> that.

Ok, will do that for the next iteration of the patchset (i don't think
i need to resubmit now with this change only, no?)

Thanks.
-- 
Yann Cantin
A4FEB47F
--

  reply	other threads:[~2012-08-03 12:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-02 12:59 [RFC ebeam PATCH v2 0/3] new USB eBeam input driver Yann Cantin
2012-08-02 12:59 ` [RFC ebeam PATCH v2 1/3] hid: hid-ids.h: Add vendor and device ID for eBeam classic device Yann Cantin
     [not found] ` <1343912397-18353-1-git-send-email-yann.cantin-QFKgK+z4sOrR7s880joybQ@public.gmane.org>
2012-08-02 12:59   ` [RFC ebeam PATCH v2 2/3] hid: hid-core.c: Blackist " Yann Cantin
2012-08-02 12:59     ` Yann Cantin
2012-08-02 12:59 ` [RFC ebeam PATCH v2 3/3] input: misc: New USB eBeam input driver Yann Cantin
2012-08-03 12:25   ` Jiri Kosina
     [not found]     ` <alpine.LRH.2.00.1208031424250.15211-1ReQVI26iDCaZKY3DrU6dA@public.gmane.org>
2012-08-03 15:30       ` Yann Cantin
2012-08-03 15:30         ` Yann Cantin
2012-08-13  9:06         ` Jiri Kosina
2012-08-02 14:16 ` [RFC ebeam PATCH v2 0/3] new " Jiri Kosina
2012-08-03 12:13   ` Yann Cantin [this message]
2012-08-03 12:13     ` Yann Cantin

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=501BC063.9040502@laposte.net \
    --to=yann.cantin@laposte.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jkosina@suse.cz \
    --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.