On Wed, Nov 07, 2012 at 03:02:39PM +0100, Jiri Kosina wrote:
> On Wed, 7 Nov 2012, Forest Bond wrote:
>
> > > /*
> > > * bla
> > > * bla
> > > */
> > >
> > > WBR, Sergei
> >
> > Thanks for the feedback. I had scanned the file and saw both styles. It
> > would
> > be nice if checkpatch.pl i
On Wed, 7 Nov 2012, Forest Bond wrote:
> > /*
> > * bla
> > * bla
> > */
> >
> > WBR, Sergei
>
> Thanks for the feedback. I had scanned the file and saw both styles. It
> would
> be nice if checkpatch.pl issued a warning for this.
>
> Jiri, would you like me to resend?
Not necessary, min
Hi Sergei,
On Wed, Nov 07, 2012 at 03:29:16PM +0400, Sergei Shtylyov wrote:
> Hello.
>
> On 06-11-2012 22:41, Forest Bond wrote:
>
> >From: Forest Bond
>
> >Previously, both usbhid and usbtouchscreen would bind to D-WAV devices
> >with class HID and protocol None, so they would be claimed by w
Hello.
On 06-11-2012 22:41, Forest Bond wrote:
From: Forest Bond
Previously, both usbhid and usbtouchscreen would bind to D-WAV devices
with class HID and protocol None, so they would be claimed by whichever
driver was loaded first. Some of these devices do in fact work with
usbhid, but no
On Tue, 6 Nov 2012, Forest Bond wrote:
> From: Forest Bond
>
> Previously, both usbhid and usbtouchscreen would bind to D-WAV devices
> with class HID and protocol None, so they would be claimed by whichever
> driver was loaded first. Some of these devices do in fact work with
> usbhid, but not
From: Forest Bond
Previously, both usbhid and usbtouchscreen would bind to D-WAV devices
with class HID and protocol None, so they would be claimed by whichever
driver was loaded first. Some of these devices do in fact work with
usbhid, but not all of them do. OTOH they all work with usbtouchsc
