All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>
To: Jiri Kosina <jkosina-AlSwsSmVLrQ@public.gmane.org>
Cc: linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Chen Peter <B29397-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
	Greg KH <greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH 2/2] input: usb: hid: Add quirk for Freescale i.MX28 ROM recovery
Date: Wed, 21 Nov 2012 16:30:38 +0100	[thread overview]
Message-ID: <201211211630.38238.marex@denx.de> (raw)
In-Reply-To: <alpine.LNX.2.00.1208151036130.7026-ztGlSCb7Y1iN3ZZ/Hiejyg@public.gmane.org>

Dear Jiri Kosina,

> On Sun, 5 Aug 2012, Marek Vasut wrote:
> > > diff --git a/drivers/hid/usbhid/hid-quirks.c
> > > b/drivers/hid/usbhid/hid-quirks.c index 903eef3..6a09570 100644
> > > --- a/drivers/hid/usbhid/hid-quirks.c
> > > +++ b/drivers/hid/usbhid/hid-quirks.c
> > > @@ -101,6 +101,7 @@ static const struct hid_blacklist {
> > > 
> > >  	{ USB_VENDOR_ID_SIGMA_MICRO, USB_DEVICE_ID_SIGMA_MICRO_KEYBOARD,
> > > 
> > > HID_QUIRK_NO_INIT_REPORTS }, { USB_VENDOR_ID_KYE,
> > > USB_DEVICE_ID_KYE_MOUSEPEN_I608X, HID_QUIRK_MULTI_INPUT }, {
> > > USB_VENDOR_ID_KYE, USB_DEVICE_ID_KYE_EASYPEN_M610X,
> > > HID_QUIRK_MULTI_INPUT }, +	{ USB_VENDOR_ID_FREESCALE,
> > > USB_DEVICE_ID_FREESCALE_MX28,
> > > HID_QUIRK_NOGET }, { 0, 0 }
> > 
> > OT: btw. the comment mentioned the list should be sorted, yet it's not so
> > for a while. Maybe a sorting patch would be favored?
> 
> I have fixed the ordering and applied. Thanks,

Can we possibly include these changes into -stable releases too ? I'm not 
exactly sure how it works for linux-input, they might be applied already, if 
that's the case, sorry for the noise.

Best regards,
Marek Vasut
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2012-11-21 15:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-05 21:57 [PATCH 1/2] input: usb: hid: Bump maximum global item tag report size to 128 bytes Marek Vasut
2012-08-05 21:57 ` [PATCH 2/2] input: usb: hid: Add quirk for Freescale i.MX28 ROM recovery Marek Vasut
     [not found]   ` <1344203835-8308-2-git-send-email-marex-ynQEQJNshbs@public.gmane.org>
2012-08-05 21:59     ` Marek Vasut
     [not found]       ` <201208052359.26938.marex-ynQEQJNshbs@public.gmane.org>
2012-08-15  8:36         ` Jiri Kosina
     [not found]           ` <alpine.LNX.2.00.1208151036130.7026-ztGlSCb7Y1iN3ZZ/Hiejyg@public.gmane.org>
2012-11-21 15:30             ` Marek Vasut [this message]
     [not found]               ` <201211211630.38238.marex-ynQEQJNshbs@public.gmane.org>
2012-11-22 22:46                 ` Jiri Kosina
2012-11-22 23:02                   ` Marek Vasut
2012-08-15  8:33 ` [PATCH 1/2] input: usb: hid: Bump maximum global item tag report size to 128 bytes Jiri Kosina
2012-08-15 11:56   ` Marek Vasut

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=201211211630.38238.marex@denx.de \
    --to=marex-ynqeqjnshbs@public.gmane.org \
    --cc=B29397-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
    --cc=greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org \
    --cc=jkosina-AlSwsSmVLrQ@public.gmane.org \
    --cc=linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.