From: Marc Kleine-Budde <mkl@pengutronix.de>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, linux-can@vger.kernel.org,
kernel@pengutronix.de, Marc Kleine-Budde <mkl@pengutronix.de>
Subject: [PATCH net-next 08/22] can: length: make header self contained
Date: Mon, 15 May 2023 22:57:45 +0200 [thread overview]
Message-ID: <20230515205759.1003118-9-mkl@pengutronix.de> (raw)
In-Reply-To: <20230515205759.1003118-1-mkl@pengutronix.de>
Include the headers that "can/length.h" depends on.
Fixes: bdd2e413192d ("can: dev: move length related code into seperate file")
Link: https://lore.kernel.org/all/20230509122854.350426-1-mkl@pengutronix.de
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
---
include/linux/can/length.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/include/linux/can/length.h b/include/linux/can/length.h
index 6995092b774e..69336549d24f 100644
--- a/include/linux/can/length.h
+++ b/include/linux/can/length.h
@@ -6,6 +6,9 @@
#ifndef _CAN_LENGTH_H
#define _CAN_LENGTH_H
+#include <linux/can.h>
+#include <linux/can/netlink.h>
+
/*
* Size of a Classical CAN Standard Frame
*
--
2.39.2
next prev parent reply other threads:[~2023-05-15 20:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 20:57 [PATCH net-next 0/22] pull-request: can-next 2023-05-15 Marc Kleine-Budde
2023-05-15 20:57 ` [PATCH net-next 01/22] can: at91_can: Convert to platform remove callback returning void Marc Kleine-Budde
2023-05-17 4:10 ` patchwork-bot+netdevbpf
2023-05-15 20:57 ` [PATCH net-next 02/22] can: bxcan: " Marc Kleine-Budde
2023-05-15 20:57 ` [PATCH net-next 03/22] can: c_can: " Marc Kleine-Budde
2023-05-15 20:57 ` [PATCH net-next 04/22] can: usb: f81604: add Fintek F81604 support Marc Kleine-Budde
2023-05-15 20:57 ` [PATCH net-next 05/22] can: cc770_isa: Convert to platform remove callback returning void Marc Kleine-Budde
2023-05-15 20:57 ` [PATCH net-next 06/22] can: bxcan: Remove unnecessary print function dev_err() Marc Kleine-Budde
2023-05-15 20:57 ` [PATCH net-next 07/22] can: cc770_platform: Convert to platform remove callback returning void Marc Kleine-Budde
2023-05-15 20:57 ` Marc Kleine-Budde [this message]
2023-05-15 20:57 ` [PATCH net-next 09/22] can: ctucanfd: " Marc Kleine-Budde
2023-05-15 20:57 ` [PATCH net-next 10/22] can: flexcan: " Marc Kleine-Budde
2023-05-15 20:57 ` [PATCH net-next 11/22] can: grcan: " Marc Kleine-Budde
2023-05-15 20:57 ` [PATCH net-next 12/22] can: ifi_canfd: " Marc Kleine-Budde
2023-05-15 20:57 ` [PATCH net-next 13/22] can: janz-ican3: " Marc Kleine-Budde
2023-05-15 20:57 ` [PATCH net-next 14/22] can: m_can: " Marc Kleine-Budde
2023-05-15 20:57 ` [PATCH net-next 15/22] can: mscan: mpc5xxx_can: " Marc Kleine-Budde
2023-05-15 20:57 ` [PATCH net-next 16/22] can: rcar: " Marc Kleine-Budde
2023-05-15 20:57 ` [PATCH net-next 17/22] can: sja1000_isa: " Marc Kleine-Budde
2023-05-15 20:57 ` [PATCH net-next 18/22] can: sja1000_platform: " Marc Kleine-Budde
2023-05-15 20:57 ` [PATCH net-next 19/22] can: softing: " Marc Kleine-Budde
2023-05-15 20:57 ` [PATCH net-next 20/22] can: sun4i_can: " Marc Kleine-Budde
2023-05-15 20:57 ` [PATCH net-next 21/22] can: ti_hecc: " Marc Kleine-Budde
2023-05-15 20:57 ` [PATCH net-next 22/22] can: xilinx: " 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=20230515205759.1003118-9-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).