From: Marc Kleine-Budde <mkl@pengutronix.de>
To: linux-can@vger.kernel.org
Cc: Oliver Hartkopp <socketcan@hartkopp.net>,
Vincent Mailhol <mailhol.vincent@wanadoo.fr>,
Marc Kleine-Budde <mkl@pengutronix.de>
Subject: [net-next v3 01/15] MAINTAINERS: CAN network layer: add missing header file can-ml.h
Date: Mon, 11 Jan 2021 15:19:16 +0100 [thread overview]
Message-ID: <20210111141930.693847-2-mkl@pengutronix.de> (raw)
In-Reply-To: <20210111141930.693847-1-mkl@pengutronix.de>
This patch add the can-ml.h to the list of maintained files of the CAN network
layer.
Fixes: ffd956eef69b ("can: introduce CAN midlayer private and allocate it automatically")
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 54fcd5fe572d..c3091a91ebbf 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3960,6 +3960,7 @@ W: https://github.com/linux-can
T: git git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can.git
T: git git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git
F: Documentation/networking/can.rst
+F: include/linux/can/can-ml.h
F: include/linux/can/core.h
F: include/linux/can/skb.h
F: include/net/netns/can.h
--
2.29.2
next prev parent reply other threads:[~2021-01-11 14:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 14:19 [net-next v3 00/15] can: dev: cleanup and add CAN frame length handling support Marc Kleine-Budde
2021-01-11 14:19 ` Marc Kleine-Budde [this message]
2021-01-11 14:19 ` [net-next v3 02/15] can: dev: move driver related infrastructure into separate subdir Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 03/15] can: dev: move bittiming related code into seperate file Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 04/15] can: dev: move length " Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 05/15] can: dev: move skb related " Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 06/15] can: dev: move netlink related code " Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 07/15] can: length: convert to kernel coding style Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 08/15] can: length: can_fd_len2dlc(): simplify length calculcation Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 09/15] can: length: canfd_sanitize_len(): add function to sanitize CAN-FD data length Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 10/15] can: length: can_skb_get_frame_len(): introduce function to get data length of frame in data link layer Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 11/15] can: dev: extend struct can_skb_priv to hold CAN frame length Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 12/15] can: dev: can_put_echo_skb(): extend to handle frame_len Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 13/15] can: dev: can_get_echo_skb(): extend to return can frame length Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 14/15] can: dev: can_rx_offload_get_echo_skb(): " Marc Kleine-Budde
2021-01-11 14:19 ` [net-next v3 15/15] can: dev: add software tx timestamps Marc Kleine-Budde
2021-01-12 13:14 ` [net-next v3 00/15] can: dev: cleanup and add CAN frame length handling support Vincent MAILHOL
2021-01-12 13:28 ` 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=20210111141930.693847-2-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=socketcan@hartkopp.net \
/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;
as well as URLs for NNTP newsgroup(s).