From: Jiri Kosina <jkosina@suse.cz>
To: Stefan Achatz <erazor_de@users.sourceforge.net>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org
Subject: Re: [PATCH 2nd attempt] HID: roccat: Add support for Isku keyboard
Date: Tue, 6 Dec 2011 10:24:58 +0100 (CET) [thread overview]
Message-ID: <alpine.LNX.2.00.1112061023150.18207@pobox.suse.cz> (raw)
In-Reply-To: <1322153184.5540.8.camel@neuromancer.tessier-ashpool>
On Thu, 24 Nov 2011, Stefan Achatz wrote:
> I mailed this patch in exactly identical form on 31.08.11
> but it hasn't been applied and I got no answer whatsoever.
> So that's a reminder if it has just been missed in the
> derangement at that time.
>
> This patch adds support for Roccat Isku keyboard.
> Userland tools can be found at http://sourceforge.net/projects/roccat
I have now queued the patch.
> +config HID_ROCCAT_ISKU
> + tristate "Roccat Isku keyboard support"
> + depends on USB_HID
> + depends on HID_ROCCAT
> + ---help---
> + Support for Roccat Isku keyboard.
> +
Seeing the number of ROCCAT device drivers growing, I'd actually like to
ask you whether it'd be possible to have just one driver (with just one
Kconfig entry) for all the roccat devices (hid-roccat); this starts
polluting the Kconfig space a little bit, and we don't want to push users
to select each and every keyboard indeed. Our usual way is doing this on
per-vendor basis.
Would you be able to implement this for the next merge window?
Thanks,
--
Jiri Kosina
SUSE Labs
prev parent reply other threads:[~2011-12-06 9:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 16:46 [PATCH 2nd attempt] HID: roccat: Add support for Isku keyboard Stefan Achatz
2011-12-06 9:24 ` Jiri Kosina [this message]
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.1112061023150.18207@pobox.suse.cz \
--to=jkosina@suse.cz \
--cc=erazor_de@users.sourceforge.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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