All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Kosina <jkosina@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Don Prince <dhprince-devel@yahoo.co.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT] HID
Date: Thu, 20 May 2010 18:36:11 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.00.1005201834190.28092@pobox.suse.cz> (raw)
In-Reply-To: <alpine.LFD.2.00.1005200922020.23538@i5.linux-foundation.org>

On Thu, 20 May 2010, Linus Torvalds wrote:

> Oh, and I notice that I shouldn't blame Don - this kind of crap is 
> apparently de rigeur in the HID layer. I only noticed because this time it 
> was a clearly very specialized driver and I started wondering what that 
> odd name was.
> 
> Guys, I can understand it if it's some kind of big-name "exists 
> everywhere" thing. Doing it for big vendors like Logitech devices may make 
> sense. But don't do it for random specialized hardware. 

Well, this is basically because of your request you made 1.5 years ago.

Originally, all the quirks were sprinkled all over the generic code, 
making it unmaintainable mess. Then the quirks for paricular 
devices/device groups were separated into idividual drivers, which meant 
quite a few new config options.

When I sent you pull request with this back then, you responded with

==
As to the Kconfig options - do they really add so much space that you need 
to ask for the quirks? You didn't use to. Can you make the questions 
depend on EMBEDDED, or at least on the HID_COMPAT thing or whatever?
==

Since then, I am keeping it organized in a way that drivers, which are 
really simple, trivial and small workarounds (descriptor/parser fixes), 
are selected in 'EMBEDDED'-way automatically.

Other larger drivers, which actually implement something substantial and 
have non-trivial code size impact, are added as a normal config options.

As all this EMBEDDED handling as been initially introduced on your 
request, I am perfectly fine removing it if you don't like it anymore.

> At least ask the user "Do you want to support all the HID crap in the 
> universe" to allow people to say Yes/No once (instead of for every 
> single crazy device).

That's definitely also an option. Do you want me to redo it this way 
before you'll be pulling it?

-- 
Jiri Kosina
SUSE Labs, Novell Inc.

  reply	other threads:[~2010-05-20 16:36 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-19 12:59 [GIT] HID Jiri Kosina
2010-05-20 16:20 ` Linus Torvalds
2010-05-20 16:26   ` Linus Torvalds
2010-05-20 16:36     ` Jiri Kosina [this message]
2010-05-20 17:01       ` Linus Torvalds
2010-05-20 17:13         ` Jiri Kosina
2010-05-21 11:26         ` Jiri Kosina
  -- strict thread matches above, loose matches on Subject: below --
2014-04-02 14:19 Jiri Kosina
2014-03-17  9:31 Jiri Kosina
2014-02-18 10:30 Jiri Kosina
2013-12-13 14:12 Jiri Kosina
2013-11-27 14:53 Jiri Kosina
2013-11-15 23:22 Jiri Kosina
2013-10-21 13:40 Jiri Kosina
2013-10-07 15:51 Jiri Kosina
2013-08-09 13:24 Jiri Kosina
2013-07-31 22:54 Jiri Kosina
2013-07-04 13:27 Jiri Kosina
2013-06-12 22:22 Jiri Kosina
2013-05-10 15:17 Jiri Kosina
2013-04-30  8:32 Jiri Kosina
2013-05-10 11:47 ` Ingo Molnar
2013-05-10 11:49   ` Jiri Kosina
2013-05-10 11:52     ` Ingo Molnar
2013-05-14 18:31     ` Ingo Molnar
2013-05-14 21:23       ` Jiri Kosina
2013-05-15  9:10         ` Ingo Molnar
2013-04-04  9:06 Jiri Kosina
2013-03-27 17:04 Jiri Kosina
2013-03-08 10:34 Jiri Kosina
2013-02-21 10:14 Jiri Kosina
2013-01-31 21:42 Jiri Kosina
2012-12-12 21:53 Jiri Kosina
2012-11-16 15:43 Jiri Kosina
2012-11-08 13:01 Jiri Kosina
2012-10-31 14:50 Jiri Kosina
2012-10-01 13:16 Jiri Kosina
2012-09-22  9:41 Jiri Kosina
2012-09-07 15:16 Jiri Kosina
2012-08-23 10:10 Jiri Kosina
2012-07-24 12:01 Jiri Kosina
2012-07-19 13:34 Jiri Kosina
2012-06-26 10:08 Jiri Kosina
2012-05-22  9:49 Jiri Kosina
2012-04-20  9:53 Jiri Kosina
2012-03-20 22:55 Jiri Kosina
2012-03-05 13:40 Jiri Kosina
2012-02-06 15:29 Jiri Kosina
2012-01-05 21:39 Jiri Kosina
2012-01-08  5:56 ` Jeremy Fitzhardinge
2012-01-08 12:29 ` Jeremy Fitzhardinge
2012-01-08 16:45   ` Jiri Kosina
2012-01-14  7:45     ` Jeremy Fitzhardinge
2012-02-01 11:48       ` Jiri Kosina
2012-02-01 17:10         ` Jeremy Fitzhardinge
2012-02-03 22:56   ` Jiri Kosina
2011-12-02 16:03 Jiri Kosina
2011-11-03 10:49 Jiri Kosina
2011-10-25  9:23 Jiri Kosina
2011-09-07 22:31 Jiri Kosina
2011-08-24 18:10 Jiri Kosina
2011-07-22 21:05 Jiri Kosina
2011-06-27 13:41 Jiri Kosina
2011-06-17 15:36 Jiri Kosina
2011-05-23 12:33 Jiri Kosina
2011-04-06 21:36 Jiri Kosina
2011-03-18 13:24 Jiri Kosina
2011-01-08 15:29 Jiri Kosina
2011-01-12  8:49 ` Jiri Kosina
2010-12-03  1:24 Jiri Kosina
2010-12-03  1:56 ` Linus Torvalds
2010-10-23 21:39 Jiri Kosina
2010-10-23 23:09 ` Jarod Wilson
2010-10-24  6:19   ` Jiri Kosina
2010-11-07  3:26     ` Jarod Wilson
2010-10-15 14:14 Jiri Kosina
2010-09-14  9:05 Jiri Kosina
2010-08-18 22:00 Jiri Kosina
2010-08-04 14:34 Jiri Kosina
2010-07-12 16:58 Jiri Kosina
2010-05-26 11:24 Jiri Kosina
2010-05-07 21:39 Jiri Kosina
2010-05-10  6:40 ` Jiri Kosina
2010-04-02 14:38 Jiri Kosina
2010-03-16 14:19 Jiri Kosina
2010-02-25 16:43 Jiri Kosina
2010-01-13 12:52 Jiri Kosina
2009-12-07 17:53 Jiri Kosina
2009-04-30 14:00 Jiri Kosina
2009-05-01 22:14 ` Jiri Kosina

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=alpine.LNX.2.00.1005201834190.28092@pobox.suse.cz \
    --to=jkosina@suse.cz \
    --cc=dhprince-devel@yahoo.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.