From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47855) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YfQu1-00008r-EY for qemu-devel@nongnu.org; Tue, 07 Apr 2015 06:38:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YfQtx-0005IG-Ds for qemu-devel@nongnu.org; Tue, 07 Apr 2015 06:38:41 -0400 Received: from cantor2.suse.de ([195.135.220.15]:45294 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YfQtx-0005I5-7V for qemu-devel@nongnu.org; Tue, 07 Apr 2015 06:38:37 -0400 Message-ID: <5523B3AB.7020007@suse.de> Date: Tue, 07 Apr 2015 12:38:35 +0200 From: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH] PING - add 1394 support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Itamar Tal , qemu-devel@nongnu.org Cc: kraxel@redhat.com, Pavel Gurvich Hi, Am 07.04.2015 um 10:18 schrieb Itamar Tal: > Hi, >=20 > Haven't got any response to this patch and couldn't find relevant > maintainer as well. Can anyone direct me to the right guy? >=20 > Thanks, >=20 > Itamar Tal, > Guardicore >=20 > On Mon, Mar 23, 2015 at 6:07 PM, Itamar Tal > wrote: >=20 > From 9c4425d4145ac6b0a2d19a6fdf5803dd13f1fa93 Mon Sep 17 00:00:00 2= 001 > From: Itamar Tal > > Date: Mon, 23 Mar 2015 14:26:47 +0200 > Subject: [PATCH] add 1394 support >=20 > This patch add 1394 (firewire) support to x86_64 and i386 qemu > softmmu. It allows one virtual machine to be the server side and th= e > other to be the client side, connected by TCP stream socket (same > thing is possible using serial port). This is very useful in for > allowing legacy devices to communicate over the firewire channel, b= ut > doesn't support USB communication. Especially, it's useful for remo= te > Windows kernel debugging over qemu for malware analysis and so on..= . > The patch was tested on major stable version 2.0.0, 2.2.1 and curre= nt > master (2.3.0rc?). >=20 > Itamar Tal, > Guardicore >=20 > --- > hw/1394/Makefile.objs | 7 + > hw/1394/hcd-ohci.c | 1645 > +++++++++++++++++++++++++++++++++++++++++++++++++ > hw/1394/hcd-ohci.h | 147 +++++ > hw/Makefile.objs | 1 + > 4 files changed, 1800 insertions(+) > create mode 100644 hw/1394/Makefile.objs > create mode 100644 hw/1394/hcd-ohci.c > create mode 100644 hw/1394/hcd-ohci.h [snip] Somehow this message does not appear threaded to such a patch... Don't top-post. Don't use HTML mails. Read SubmittingPatches - it specifically states that we cannot accept patches that are not signed off. Also, your commit message needs to be overhauled, and the patch did not arrive the right way - looks like you did not use git-send-email but instead pasted a patch file into an email, which caused linewrap damage and wrongly added the headers into what would be the commit message. Information on where/how the patch was tested and your name/company belongs below --- or into a separate (threaded!) cover letter, not into the commit message. Since you're implementing a new bus, there is no predefined maintainer to review this... and as long as we're in Hard Freeze for v2.3 review may take some time. Regards, Andreas --=20 SUSE Linux GmbH, Maxfeldstr. 5, 90409 N=C3=BCrnberg, Germany GF: Felix Imend=C3=B6rffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton; HRB 21284 (AG N=C3=BCrnberg)