From: Pavel Pisa <pisa@cmp.felk.cvut.cz>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: qemu-devel@nongnu.org, Marek Vasut <marex@denx.de>,
Oliver Hartkopp <socketcan@hartkopp.net>,
Stefan Hajnoczi <stefanha@gmail.com>,
Deniz Eren <deniz.eren@icloud.com>,
Konrad Frederic <frederic.konrad@adacore.com>,
Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [Qemu-devel] [PATCH 0/5 v2] CAN bus support for QEMU (SJA1000 PCI so far)
Date: Thu, 2 Nov 2017 03:10:27 +0100 [thread overview]
Message-ID: <201711020310.27240.pisa@cmp.felk.cvut.cz> (raw)
In-Reply-To: <844921c2-2855-207a-2f9f-7c2ad28187e6@amsat.org>
Hello Philippe,
On Thursday 02 of November 2017 02:27:18 Philippe Mathieu-Daudé wrote:
> On 11/01/2017 10:00 PM, pisa@cmp.felk.cvut.cz wrote:
> > Some page about the project
> >
> > https://gitlab.fel.cvut.cz/canbus/qemu-canbus/wikis/home
> >
> > FEE CTU GitLab repository with can-pci branch for 2.3, 2.4, 2.7, 2.8 and
> > 2.10 version if QEMU is available there
> >
> > https://gitlab.fel.cvut.cz/canbus/qemu-canbus/tree/can-pci
>
> This GitLab seems to be restricted to your university :(
Thanks fort the report, I have moved work from GitHub to local GitLab
for future continuous integration support.
Repository has been public from beginning, but I forgot
to make wiki public. It should be OK now.
Unfortunately, my attempt to follow suggestion to ensure
that even conditionalized debug code is build always
leads to patchew.org problem report because now exposed
static function is not used in non Linux builds
/tmp/qemu-test/src/hw/can/can_core.c:153:13: error: 'can_display_msg' defined but not used [-Werror=unused-function]
static void can_display_msg(struct qemu_can_frame *msg)
^~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
It is used for connection to the host CAN bus interface
and that is implemented only for SocketCAN on Linux.
So patches v3 series is necessary anyway.
I would be happy if I receive some review remarks
for this reorganized series to lower iteration count.
Thanks in advance,
Pavel
next prev parent reply other threads:[~2017-11-02 2:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 1:00 [Qemu-devel] [PATCH 0/5 v2] CAN bus support for QEMU (SJA1000 PCI so far) pisa
2017-11-02 1:00 ` [Qemu-devel] [PATCH 1/5] CAN bus simple messages transport implementation for QEMU pisa
2017-11-02 1:53 ` Philippe Mathieu-Daudé
2017-11-02 2:06 ` Philippe Mathieu-Daudé
2017-11-02 1:00 ` [Qemu-devel] [PATCH 2/5] CAN bus SJA1000 chip register level emulation " pisa
2017-11-02 2:40 ` Philippe Mathieu-Daudé
2017-11-02 1:00 ` [Qemu-devel] [PATCH 3/5] CAN bus Kvaser PCI CAN-S (single SJA1000 channel) emulation added pisa
2017-11-02 2:46 ` Philippe Mathieu-Daudé
2017-11-02 1:00 ` [Qemu-devel] [PATCH 4/5] CAN bus PCM-3680I PCI (dual " pisa
2017-11-02 1:01 ` [Qemu-devel] [PATCH 5/5] CAN bus MIOe-3680 " pisa
2017-11-02 1:21 ` [Qemu-devel] [PATCH 0/5 v2] CAN bus support for QEMU (SJA1000 PCI so far) no-reply
2017-11-02 1:27 ` Philippe Mathieu-Daudé
2017-11-02 2:10 ` Pavel Pisa [this message]
2017-11-02 3:17 ` Philippe Mathieu-Daudé
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=201711020310.27240.pisa@cmp.felk.cvut.cz \
--to=pisa@cmp.felk.cvut.cz \
--cc=deniz.eren@icloud.com \
--cc=f4bug@amsat.org \
--cc=frederic.konrad@adacore.com \
--cc=jan.kiszka@siemens.com \
--cc=marex@denx.de \
--cc=qemu-devel@nongnu.org \
--cc=socketcan@hartkopp.net \
--cc=stefanha@gmail.com \
/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).