From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
wg@grandegger.com, kernel@martin.sperl.org,
linux-can@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] Add Microchip MCP25XXFD CAN driver
Date: Mon, 22 Jun 2020 12:55:41 +0200 [thread overview]
Message-ID: <c5fc46c1-abaf-cf67-abb6-0077bafdff3a@pengutronix.de> (raw)
In-Reply-To: <20200622102559.GA3077@x1.vandijck-laurijssen.be>
On 6/22/20 12:25 PM, Kurt Van Dijck wrote:
> I got my board up with a 5.7, despite device-tree problems completely
> unrelated to CAN.
\o/
> It seems to work well with a fully-loaded CAN bus (cangen -g0 ...).
> So that is a real improvement.
Can I add your Tested-by?
> I will need to add the listen-only mode soon.
Patches are always welcome!
regards,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2020-06-22 10:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 7:44 Manivannan Sadhasivam
2020-06-10 7:44 ` [PATCH 1/6] dt-bindings: can: Document devicetree bindings for MCP25XXFD Manivannan Sadhasivam
2020-06-10 7:44 ` [PATCH 2/6] can: mcp25xxfd: Add Microchip MCP25XXFD CAN-FD driver infrastructure Manivannan Sadhasivam
2020-06-10 7:44 ` [PATCH 3/6] can: mcp25xxfd: Add support for CAN reception Manivannan Sadhasivam
2020-06-10 7:44 ` [PATCH 4/6] can: mcp25xxfd: Add CAN transmission support Manivannan Sadhasivam
2020-06-10 7:44 ` [PATCH 5/6] can: mcp25xxfd: Optimize TEF read by avoiding unnecessary SPI transfers Manivannan Sadhasivam
2020-06-10 7:44 ` [PATCH 6/6] MAINTAINERS: Add entry for Microchip MCP25XXFD CAN network driver Manivannan Sadhasivam
2020-06-11 16:26 ` [PATCH 0/6] Add Microchip MCP25XXFD CAN driver Marc Kleine-Budde
2020-06-11 20:30 ` Marc Kleine-Budde
2020-06-12 11:27 ` Marc Kleine-Budde
2020-06-17 16:59 ` Kurt Van Dijck
2020-06-17 22:36 ` Marc Kleine-Budde
2020-06-18 12:30 ` Kurt Van Dijck
2020-06-18 12:35 ` Marc Kleine-Budde
2020-06-22 10:25 ` Kurt Van Dijck
2020-06-22 10:55 ` Marc Kleine-Budde [this message]
2020-06-22 12:30 ` Kurt Van Dijck
2020-06-22 12:43 ` Kurt Van Dijck
2020-06-22 12:54 ` Marc Kleine-Budde
2020-06-22 13:26 ` Kurt Van Dijck
2020-06-22 13:41 ` Marc Kleine-Budde
2020-06-18 8:55 ` Manivannan Sadhasivam
2020-06-20 2:43 ` Manivannan Sadhasivam
2020-06-22 11:47 ` Marc Kleine-Budde
2020-06-18 12:06 ` Manivannan Sadhasivam
2020-06-22 11:41 ` Marc Kleine-Budde
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=c5fc46c1-abaf-cf67-abb6-0077bafdff3a@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=kernel@martin.sperl.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=netdev@vger.kernel.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
all inboxes | Powered by JetHome®