From: Harald Mommer <Harald.Mommer@opensynergy.com>
To: virtio-dev@lists.oasis-open.org, linux-can@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Wolfgang Grandegger <wg@grandegger.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Dariusz Stojaczyk <Dariusz.Stojaczyk@opensynergy.com>
Subject: [virtio-dev] [RFC PATCH v2 0/2] can: virtio: virtio-can driver
Date: Fri, 4 Nov 2022 18:24:19 +0100 [thread overview]
Message-ID: <20221104172421.8271-1-Harald.Mommer@opensynergy.com> (raw)
Hello,
this is a new virtio-can driver.
The proposed addition to the virtio specification which should match
this driver has been sent 25-Aug-2022 and can be found here:
https://lore.kernel.org/all/20220825133410.18367-1-harald.mommer@opensynergy.com/
(Got no comments on the updated specification proposal now.)
The RFC driver version has been sent 25-Aug-2022 and can be found here:
https://lore.kernel.org/all/20220825134449.18803-1-harald.mommer@opensynergy.com/
- Small update to be compilable against newest kernel
- netif_napi_add() prototype change
- Address the review comments got from Arnd Bergmann, Oliver Hartkopp,
Marc Kleine-Budde:
- Remove virtio_can_hexdump()
- Use completion instead of polling
- Restructure usage of spinlock in virtio_can_start_xmit()
- Save kicks in virtio_can_start_xmit()
- Minimize usage of BUG_ON()
- Make driver less noisy
- Move register_virtio_candev() down in code
- Remove unwanted MISRA habits used to in a former life
- Treat bitmasks as bitmasks
- Remove excessive usage of netdev_warn() silently sanitizing
- Fix RTR frame handling with payload != 0
- Work through checkpatch problems
- Clarify license
- Remove some pointless leftover comments
Regards
Harald
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next reply other threads:[~2022-11-04 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 17:24 Harald Mommer [this message]
2022-11-04 17:24 ` [virtio-dev] [RFC PATCH v2 1/2] can: virtio: Initial virtio CAN driver Harald Mommer
[not found] ` <4782632.31r3eYUQgx@steina-w>
[not found] ` <CAMZ6RqLALOYFWQJ4C4HTaRw7y-waUbqOX0WzrWVNiQG51QexHw@mail.gmail.com>
2023-05-17 11:43 ` [virtio-dev] " Harald Mommer
2022-11-04 17:24 ` [virtio-dev] [RFC PATCH v2 2/2] can: virtio: Add virtio_can to MAINTAINERS file Harald Mommer
[not found] ` <CAMZ6RqLUCs0W8ZP2jAUsFMUXgHTjce649Gu+jnz_S1x_0ER6YQ@mail.gmail.com>
2022-11-08 19:13 ` [virtio-dev] " Harald Mommer
2022-11-08 19:22 ` Harald Mommer
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=20221104172421.8271-1-Harald.Mommer@opensynergy.com \
--to=harald.mommer@opensynergy.com \
--cc=Dariusz.Stojaczyk@opensynergy.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=wg@grandegger.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