Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932556AbZKRTAe (ORCPT ); Wed, 18 Nov 2009 14:00:34 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932536AbZKRTAe (ORCPT ); Wed, 18 Nov 2009 14:00:34 -0500 Received: from einhorn.in-berlin.de ([192.109.42.8]:35601 "EHLO einhorn.in-berlin.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758311AbZKRTAc (ORCPT ); Wed, 18 Nov 2009 14:00:32 -0500 X-Envelope-From: stefanr@s5r6.in-berlin.de Date: Wed, 18 Nov 2009 20:00:18 +0100 (CET) From: Stefan Richter Subject: [PATCH 0/6] DVB: firedtv: simplifications and a portability fix To: linux-media@vger.kernel.org cc: linux1394-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-Disposition: INLINE Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1151 Lines: 30 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/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/