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: Thu, 18 Jun 2020 14:35:28 +0200 [thread overview]
Message-ID: <c8267280-e7a9-8171-d714-fa392ccb5537@pengutronix.de> (raw)
In-Reply-To: <20200618123055.GA17496@x1.vandijck-laurijssen.be>
On 6/18/20 2:30 PM, Kurt Van Dijck wrote:
> On do, 18 jun 2020 00:36:29 +0200, Marc Kleine-Budde wrote:
>> On 6/17/20 6:59 PM, Kurt Van Dijck wrote:
>>> I'm in the process of getting a Variscite imx8m mini SOM online, with
>>
>> Have your heard about the imx8m plus? It has CAN cores! We have a board in the
>> office to play with. :)
>>
>>> MCP2517FD. The 4.19 kernel that comes with it, has a driver that is
>>
>> You shall not start projects with 1,5 years old kernel.
>> And you probably shall not use vendor kernel for new projects.
>> :D
>
> your rpi kernel starts of v4.19.119 (or so), where the variscite starts
> of v4.19.35.
You're missing some stable backports for the kernel then.
> The result was quite some list of merge conflicts, on top of a vendor
> kernel, so I took your advise and switched to the latest and greatest
> 5.7.3.
\o/
> Luckily, we need no sound (yet) and no video. :-)
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-18 12:35 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 [this message]
2020-06-22 10:25 ` Kurt Van Dijck
2020-06-22 10:55 ` Marc Kleine-Budde
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=c8267280-e7a9-8171-d714-fa392ccb5537@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®