From: Markus Armbruster <armbru@redhat.com>
To: pisa@cmp.felk.cvut.cz
Cc: Marek Vasut <marex@denx.de>, Jiri Novak <jnovak@fel.cvut.cz>,
Stefan Hajnoczi <stefanha@gmail.com>,
Deniz Eren <deniz.eren@icloud.com>,
qemu-devel@nongnu.org, Oleksij Rempel <o.rempel@pengutronix.de>,
Konrad Frederic <frederic.konrad@adacore.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
Jan Charvat <charvj10@fel.cvut.cz>,
Oliver Hartkopp <socketcan@hartkopp.net>,
Paolo Bonzini <pbonzini@redhat.com>,
Ondrej Ille <ondrej.ille@gmail.com>
Subject: Re: [PATCH v1 0/6] CTU CAN FD core support
Date: Thu, 30 Jul 2020 17:29:51 +0200 [thread overview]
Message-ID: <878sf1vx5c.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <cover.1594725647.git.pisa@cmp.felk.cvut.cz> (pisa@cmp.felk.cvut.cz's message of "Tue, 14 Jul 2020 14:20:13 +0200")
This series needs review. Any takers?
prev parent reply other threads:[~2020-07-30 15:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 12:20 [PATCH v1 0/6] CTU CAN FD core support pisa
2020-07-14 12:20 ` [PATCH v1 1/6] net/can: Initial host SocketCan support for CAN FD pisa
2020-09-01 20:01 ` Vikram Garhwal
2020-09-02 7:51 ` Pavel Pisa
2020-09-03 5:20 ` Vikram Garhwal
2020-09-03 5:29 ` Vikram Garhwal
2020-07-14 12:20 ` [PATCH v1 2/6] hw/net/can: sja1000 ignore CAN FD frames pisa
2020-09-01 17:07 ` Vikram Garhwal
2020-07-14 12:20 ` [PATCH v1 3/6] net/can: Add can_dlc2len and can_len2dlc for CAN FD pisa
2020-09-03 5:43 ` Vikram Garhwal
2020-09-03 6:12 ` Pavel Pisa
2020-09-03 6:38 ` Vikram Garhwal
2020-07-14 12:20 ` [PATCH v1 4/6] hw/net/can/ctucafd: Add CTU CAN FD core register definitions pisa
2020-07-14 12:20 ` [PATCH v1 5/6] hw/net/can: CTU CAN FD IP open hardware core emulation pisa
2020-07-24 9:46 ` Pavel Pisa
2020-07-14 12:20 ` [PATCH v1 6/6] hw/net/can: Documentation for " pisa
2020-07-14 12:47 ` [PATCH v1 0/6] CTU CAN FD core support no-reply
2020-07-14 13:45 ` [PATCH v1 0/6] CTU CAN FD core support - patchew report Pavel Pisa
2020-07-14 12:48 ` [PATCH v1 0/6] CTU CAN FD core support no-reply
2020-07-30 15:29 ` Markus Armbruster [this message]
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=878sf1vx5c.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=charvj10@fel.cvut.cz \
--cc=deniz.eren@icloud.com \
--cc=frederic.konrad@adacore.com \
--cc=jan.kiszka@siemens.com \
--cc=jnovak@fel.cvut.cz \
--cc=marex@denx.de \
--cc=o.rempel@pengutronix.de \
--cc=ondrej.ille@gmail.com \
--cc=pbonzini@redhat.com \
--cc=pisa@cmp.felk.cvut.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.