From: Ping <pinglinux@gmail.com>
To: linux-serial@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 2/2] serial/8250_pnp: Use wildcard for serial Wacom tablets
Date: Mon, 11 Jan 2010 11:51:29 -0800 [thread overview]
Message-ID: <167e8a331001111151r68ba389by2757a74db2e44b91@mail.gmail.com> (raw)
In-Reply-To: <167e8a331001071652q45313e9bj30606a023b8fb29@mail.gmail.com>
Sorry to send this patchset more than once. It didn't land in Linus
tree last year.
Ping
From: Matthew Garrett <mjg@redhat.com>
Date: Thu, 7 Jan 2010 16:30:08 -0800
Subject: [PATCH 2/2] 8250_pnp: Use wildcard for serial Wacom tablets
Wacom claims that the WACF namespace will always be devoted to
serial Wacom tablets. Remove the existing entries and add a
wildcard to avoid having to update the kernel every time they
add a new device.
Signed-off-by: Matthew Garrett <mjg@redhat.com>
Tested-by: Ping Cheng <pingc@wacom.com>
Signed-off-by: Ping Cheng <pingc@wacom.com>
---
drivers/serial/8250_pnp.c | 10 +---------
1 files changed, 1 insertions(+), 9 deletions(-)
diff --git a/drivers/serial/8250_pnp.c b/drivers/serial/8250_pnp.c
index b5496a1..cbe17c8 100644
--- a/drivers/serial/8250_pnp.c
+++ b/drivers/serial/8250_pnp.c
@@ -328,15 +328,7 @@ static const struct pnp_device_id pnp_dev_table[] = {
/* U.S. Robotics 56K Voice INT PnP*/
{ "USR9190", 0 },
/* Wacom tablets */
- { "WACF004", 0 },
- { "WACF005", 0 },
- { "WACF006", 0 },
- { "WACF007", 0 },
- { "WACF008", 0 },
- { "WACF009", 0 },
- { "WACF00A", 0 },
- { "WACF00B", 0 },
- { "WACF00C", 0 },
+ { "WACFXXX", 0 },
/* Compaq touchscreen */
{ "FPI2002", 0 },
/* Fujitsu Stylistic touchscreens */
--
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
parent reply other threads:[~2010-01-11 19:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <167e8a331001071652q45313e9bj30606a023b8fb29@mail.gmail.com>]
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=167e8a331001111151r68ba389by2757a74db2e44b91@mail.gmail.com \
--to=pinglinux@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-serial@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).