From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux-media@vger.kernel.org
Cc: linux1394-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: [PATCH 0/6] DVB: firedtv: simplifications and a portability fix
Date: Wed, 18 Nov 2009 20:00:18 +0100 (CET) [thread overview]
Message-ID: <tkrat.7dc1f889fd1b69ad@s5r6.in-berlin.de> (raw)
The following three patches are applicable after "firedtv: port to new
firewire core" from 2009-11-08:
[PATCH 1/6] firedtv: shrink buffer pointer table
[PATCH 2/6] firedtv: packet requeuing is likely to succeed
[PATCH 3/6] firedtv: remove an unnecessary function argument
The rest of this patch set additionally requires the latest firedtv as
of 2.6.32-rc7:
[PATCH 4/6] firedtv: do not DMA-map stack addresses
[PATCH 5/6] firedtv: remove check for interrupting signal
[PATCH 6/6] firedtv: reduce memset()s
drivers/media/dvb/firewire/firedtv-1394.c | 13
drivers/media/dvb/firewire/firedtv-avc.c | 520 +++++++++++-----------
drivers/media/dvb/firewire/firedtv-dvb.c | 1
drivers/media/dvb/firewire/firedtv-fw.c | 39 -
drivers/media/dvb/firewire/firedtv.h | 8
5 files changed, 306 insertions(+), 275 deletions(-)
--
Stefan Richter
-=====-==--= =-== =--=-
http://arcgraph.de/sr/
next reply other threads:[~2009-11-18 19:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 19:00 Stefan Richter [this message]
2009-11-18 19:00 ` [PATCH 1/6] firedtv: shrink buffer pointer table Stefan Richter
2009-11-18 19:01 ` [PATCH 2/6] firedtv: packet requeuing is likely to succeed Stefan Richter
2009-11-18 19:01 ` [PATCH 3/6] firedtv: remove an unnecessary function argument Stefan Richter
2009-11-18 19:02 ` [PATCH 4/6] firedtv: do not DMA-map stack addresses Stefan Richter
2009-11-18 19:03 ` [PATCH 5/6] firedtv: remove check for interrupting signal Stefan Richter
2009-11-18 19:03 ` [PATCH 6/6] firedtv: reduce memset()s Stefan Richter
2009-11-21 0:26 ` [PATCH 0/6] DVB: firedtv: simplifications and a portability fix Stefan Richter
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=tkrat.7dc1f889fd1b69ad@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.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
all inboxes | Powered by JetHome®