From: bart.hartgers@gmail.com
To: Greg Kroah-Hartman <gregkh@suse.de>, Mike McCormack <mikem@ring3k.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/6] ark3116: (v2) driver rework after review
Date: Wed, 28 Oct 2009 10:43:24 +0100 [thread overview]
Message-ID: <20091028094324.010816897@gmail.com> (raw)
Hi Greg,
I updated my ark3116 patches after the review on the list. The main
change is the removal of the atomic_t fields and addition of a spinlock.
This patch set brings the ark3116 driver up to date by:
- replacing the magic numbers by proper uart register accesses
- introducing locking
- line error handling
- interrupt based modem status handling
- cts/rts handshaking
- break signaling
The patches are against 2.6.32-rc4.
Mike: do you still want to combine these with yours?: if so, let me
know if I can help with merging them.
Groeten,
Bart
--
next reply other threads:[~2009-10-28 9:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 9:43 bart.hartgers [this message]
2009-10-28 9:43 ` [PATCH 1/6] ark3116: (v2) Setup some basic infrastructure for new ark3116 driver bart.hartgers
2009-10-28 9:43 ` [PATCH 2/6] ark3116: (v2) Make existing functions 16450-aware and add close and release functions bart.hartgers
2009-10-28 9:43 ` [PATCH 3/6] ark3116: (v2) Replace cmget bart.hartgers
2009-10-28 9:43 ` [PATCH 4/6] ark3116: (v2) Add cmset and break bart.hartgers
2009-10-28 9:43 ` [PATCH 5/6] ark3116: (v2) Callbacks for interrupt and bulk read bart.hartgers
2009-10-28 9:43 ` [PATCH 6/6] ark3116: (v2) Cleanup of now unneeded functions bart.hartgers
2009-10-28 11:41 ` [PATCH 0/6] ark3116: (v2) driver rework after review Mike McCormack
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=20091028094324.010816897@gmail.com \
--to=bart.hartgers@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mikem@ring3k.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.