Not a problem to do, I though you were asking Bastian about it. While I'm at
it would you like me to consolidate all the kernel versions down to one. I
already did this based on the 0.8.5-4 release and test compiled the combined
source against kernel 2.6.9 thru 2.6.31. It would just be a matter of
incorporating the 0.8.5-9 changes into those source files and updating the
Makefile system.
It would make life simpler that having to backport changes to all the
separate kernel source directories.

Jason

On Jan 20, 2010 4:10 PM, "Ping Cheng" <pingli...@gmail.com> wrote:

On Tue, Jan 19, 2010 at 8:21 PM, Jason Childs <
obliv...@users.sourceforge.net> wrote:

> > > > 0001-Input-wacom-Debian-patch-for-device-ids.patch > > > > No real
comment on this one.  It ...

I have a quick question for this patch:  how difficult or reasonable would
it be for you to keep both the wacom_features_0x00 (etc.) and wacom_ids in
wacom_wac.c instead of moving to wacom_sys.c?

It makes much more sense to me, as a driver maintainer, to leave those two
sets of entity in wacom_wac,c since it can be shared among kernel releases.
The wacom_sys.c changes out of my control. But the good thing is that I
normally don't need to worry about those changes myself since kernel/input
maintainers would do the work for us.

Do you see my picture?  I've asked this question in the other email thread
that you've cc'd to.  Hope you don't feel too annoyed by hearing it again.

Ping
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Reply via email to