qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
	Pavel Pisa <pisa@cmp.felk.cvut.cz>
Cc: Oliver Hartkopp A <socketcan@hartkopp.net>,
	jinyang.sia@gmail.com,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	linux-can@vger.kernel.org, rtems-devel@rtems.org,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Stefan Weil <sw@weilnetz.de>, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] CAN bus simple SJA1000 PCI card emulation for QEMU
Date: Mon, 12 May 2014 11:18:09 +0200	[thread overview]
Message-ID: <537091D1.4080004@suse.de> (raw)
In-Reply-To: <CAEgOgz7sCAWuyVFOR94omp=2DEpisio+nUQDWBCzq3e-Y_WCVw@mail.gmail.com>

Am 12.05.2014 11:01, schrieb Peter Crosthwaite:
> On Sat, May 10, 2014 at 4:14 AM, Pavel Pisa <pisa@cmp.felk.cvut.cz> wrote:
>> The work is based on Jin Yang GSoC 2013 work funded
>> by Google and mentored in frame of RTEMS project GSoC
>> slot donated to QEMU.

Should/can that be recorded in form of his Signed-off-by before yours?

>> Update from QEMU-1.4 version and architecture cleanup
>> by Pavel Pisa (Czech Technical University in Prague).
>>
>> The core SJA1000 support is independent of provided
>> PCI board. The simple core CAN bus infrastructure
>> is independent as well.
>>
>> Connection to the real host CAN bus network through
>> SocketCAN network interface is available for Linux
>> host system as well.
>>
>> Signed-off-by: Pavel Pisa <pisa@cmp.felk.cvut.cz>
>> ---
>>  default-configs/pci.mak |   2 +
>>  hw/net/Makefile.objs    |   4 +
>>  hw/net/can_core.c       | 350 +++++++++++++++++++
>>  hw/net/can_pci.c        | 238 +++++++++++++
>>  hw/net/can_sja1000.c    | 878 ++++++++++++++++++++++++++++++++++++++++++++++++
>>  hw/net/can_sja1000.h    | 163 +++++++++
>>  include/net/can_emu.h   | 123 +++++++
>>  7 files changed, 1758 insertions(+)
> 
> That's a big patch. And it seems to add a new API/framework, then new
> users of that API. Can you add your core as a single patch, then
> incrementally bring your devices stuff as subsequent patches? My guess
> is this should be about 3 patches - are there any circular deps,
> requiring you to bring your three c files all at once or is there a
> logical order you can add them for ease of review?

True. But before you resend, I'd like to hear Stefan H.'s view of
whether CAN should go into hw/net/ at all or into, e.g., hw/can/.

Independently of the placement, it's always an interesting question of
who will maintain this new infrastructure - I don't see any new
MAINTAINERS entries getting added in either patch (NB: a diffstat in 0/2
would've been nice) for patch review.

Regards,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2014-05-12  9:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09 18:10 [Qemu-devel] [PATCH 0/2] CAN SJA100 controller emulation and SocketCAN based host CAN bus access Pavel Pisa
2014-05-09 18:14 ` [Qemu-devel] [PATCH 1/2] CAN bus simple SJA1000 PCI card emulation for QEMU Pavel Pisa
2014-05-12  9:01   ` Peter Crosthwaite
2014-05-12  9:18     ` Andreas Färber [this message]
2014-05-09 18:15 ` [Qemu-devel] [PATCH 2/2] CAN bus Kvaser PCI CAN-S (single SJA1000 channel) emulation added Pavel Pisa
2014-05-13 12:29 ` [Qemu-devel] [PATCH 0/2] CAN SJA100 controller emulation and SocketCAN based host CAN bus access Stefan Hajnoczi
2014-05-15 13:53   ` Pavel Pisa
2014-05-23  1:52     ` [Qemu-devel] " jinyang.sia
2014-05-23  9:42     ` [Qemu-devel] [PATCH 0/2] " Stefan Hajnoczi
2014-05-23 14:25       ` Pavel Pisa

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=537091D1.4080004@suse.de \
    --to=afaerber@suse.de \
    --cc=jinyang.sia@gmail.com \
    --cc=linux-can@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=peter.crosthwaite@xilinx.com \
    --cc=pisa@cmp.felk.cvut.cz \
    --cc=qemu-devel@nongnu.org \
    --cc=rtems-devel@rtems.org \
    --cc=socketcan@hartkopp.net \
    --cc=stefanha@redhat.com \
    --cc=sw@weilnetz.de \
    /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).