From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: linux-can@vger.kernel.org
Subject: Re: [PATCH v4 6/6] can: sja1000: Add support for RZ/N1 SJA1000 CAN Controller
Date: Fri, 19 Aug 2022 13:23:22 +0200 [thread overview]
Message-ID: <04b05aa5-e926-1050-b1ed-e5ad99a23722@hartkopp.net> (raw)
In-Reply-To: <20220819084532.ywtziogd7ycuozxx@pengutronix.de>
Hi Marc,
On 8/19/22 10:45, Marc Kleine-Budde wrote:
>
> Applied to linux-can-next.
net-next has been rebased to 6.0-rc1 some house ago.
Do you have any plans for the CAN XL support for linux-can-next?
So far there has been no new feedback for a while.
https://lore.kernel.org/linux-can/20220801190010.3344-1-socketcan@hartkopp.net/T/#t
Best,
Oliver
next prev parent reply other threads:[~2022-08-19 11:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 11:52 [PATCH v4 0/6] Add support for RZ/N1 SJA1000 CAN controller Biju Das
2022-07-10 11:52 ` [PATCH v4 1/6] dt-bindings: can: sja1000: Convert to json-schema Biju Das
2022-07-12 10:19 ` Krzysztof Kozlowski
2022-07-10 11:52 ` [PATCH v4 2/6] dt-bindings: can: nxp,sja1000: Document RZ/N1{D,S} support Biju Das
2022-07-12 10:20 ` Krzysztof Kozlowski
2022-08-18 9:38 ` Geert Uytterhoeven
2022-08-24 9:12 ` Biju Das
2022-07-10 11:52 ` [PATCH v4 3/6] can: sja1000: Add Quirk for RZ/N1 SJA1000 CAN controller Biju Das
2022-07-10 11:52 ` [PATCH v4 4/6] can: sja1000: Use device_get_match_data to get device data Biju Das
2022-07-10 11:52 ` [PATCH v4 5/6] can: sja1000: Change the return type as void for SoC specific init Biju Das
2022-07-10 11:52 ` [PATCH v4 6/6] can: sja1000: Add support for RZ/N1 SJA1000 CAN Controller Biju Das
2022-07-12 12:56 ` Marc Kleine-Budde
2022-07-12 13:03 ` Biju Das
2022-07-19 18:53 ` Marc Kleine-Budde
2022-07-19 19:34 ` Biju Das
2022-08-19 8:45 ` Marc Kleine-Budde
2022-08-19 11:23 ` Oliver Hartkopp [this message]
2022-08-19 11:30 ` Marc Kleine-Budde
2022-08-19 11:42 ` Oliver Hartkopp
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=04b05aa5-e926-1050-b1ed-e5ad99a23722@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
/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