linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-input@vger.kernel.org, marcel@holtmann.org,
	linux-kernel@vger.kernel.org, anssi.hannula@gmail.com
Subject: Re: [PATCH 06/10] HID: move logitech report quirks
Date: Mon, 09 Jun 2008 12:29:50 +0200	[thread overview]
Message-ID: <484D061E.5000308@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0806041415130.10085@jikos.suse.cz>

Hi!

On 06/04/2008 02:16 PM, Jiri Kosina wrote:
> On Fri, 16 May 2008, Jiri Slaby wrote:
>> Move them from core code to a separate driver.
> is there a reason why this moves only the report descriptor 
> Logitech-specific quirks, but leaves the input mapping still in 
> hid-input-quirks.c and doesn't move it into ->input_mapping method too?

No, there is no strong reason, I just postponed it to the second round of 
changes. I wanted to hear comments first, so I only moved fully only apple 
driver (to present how the concept was thought). After things settle down, I'm 
going to move the rest of quirks including this one.

  reply	other threads:[~2008-06-09 10:29 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16  9:49 [PATCH 01/10] modpost: add support for hid Jiri Slaby
2008-05-16  9:49 ` [PATCH 02/10] HID: make a bus from hid code Jiri Slaby
2008-05-16  9:49   ` [PATCH 03/10] HID: hid, make parsing event driven Jiri Slaby
2008-05-16  9:49     ` [PATCH 04/10] HID: move ids into separate file Jiri Slaby
2008-05-16  9:49       ` [PATCH 05/10] HID: move usage input mapping to hid.h Jiri Slaby
2008-05-16  9:49         ` [PATCH 06/10] HID: move logitech report quirks Jiri Slaby
2008-05-16  9:49           ` [PATCH 07/10] HID: move ignore quirks Jiri Slaby
2008-05-16  9:49             ` [PATCH 08/10] HID: move apple quirks Jiri Slaby
2008-05-16  9:49               ` [PATCH 09/10] HID: add compat support Jiri Slaby
2008-06-04  8:55                 ` Jiri Kosina
2008-06-04  9:00                   ` Jiri Slaby
2009-01-24  5:55                 ` Jaswinder Singh Rajput
2009-01-25 13:03                   ` Jiri Slaby
2009-01-25 16:57                   ` Jiri Kosina
2009-01-25 17:11                     ` Jaswinder Singh Rajput
2008-06-04 14:13               ` [PATCH 08/10] HID: move apple quirks Jiri Kosina
2008-06-09 10:40                 ` Jiri Slaby
2008-06-04 12:16           ` [PATCH 06/10] HID: move logitech report quirks Jiri Kosina
2008-06-09 10:29             ` Jiri Slaby [this message]
2008-06-16 10:15               ` Jiri Kosina
2008-06-04 13:21           ` Jiri Kosina
2008-06-09 10:33             ` Jiri Slaby
2008-06-11 14:13               ` Jiri Kosina
2008-06-11 15:39                 ` Oliver Neukum
2008-06-11 18:35                   ` Jiri Slaby
2008-06-11 18:23                 ` Anssi Hannula
2008-05-19 13:36 ` [PATCH 01/10] modpost: add support for hid Jiri Kosina
2008-05-19 13:38   ` Jiri Slaby
2008-05-19 13:50 ` [PATCH v2] " Jiri Slaby
2008-06-05  9:26 ` [PATCH 01/10] " Jiri Kosina
2008-06-09 10:41   ` Jiri Slaby

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=484D061E.5000308@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=anssi.hannula@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).