From: Nikolai Kondrashov <spbnick@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-input <linux-input@vger.kernel.org>
Subject: Re: Merging hid-huion into hid-uclogic
Date: Tue, 27 Jan 2015 13:10:49 +0200 [thread overview]
Message-ID: <54C77239.5000508@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1501271109200.10817@pobox.suse.cz>
On 01/27/2015 12:10 PM, Jiri Kosina wrote:
> On Sun, 25 Jan 2015, Nikolai Kondrashov wrote:
>
>> I'd like to have your opinion if it will be fine to merge hid-huion.c into
>> hid-uclogic.c, keeping tablet support intact, of course.
>
> huion driver module doesn't take any module parameters, so that should be
> fine (renaming modules that accept parameters is more tricky due to
> potential userspace configuration breakage).
Thanks a lot, Jiri. I'll work towards that then.
Nick
prev parent reply other threads:[~2015-01-27 11:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-25 13:22 Merging hid-huion into hid-uclogic Nikolai Kondrashov
2015-01-27 10:10 ` Jiri Kosina
2015-01-27 11:10 ` Nikolai Kondrashov [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=54C77239.5000508@gmail.com \
--to=spbnick@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.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).