From: Ivan Vecera <ivecera@redhat.com>
To: netdev@vger.kernel.org
Cc: poros@redhat.com, mschmidt@redhat.com,
jesse.brandeburg@intel.com, anthony.l.nguyen@intel.com,
davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com, intel-wired-lan@lists.osuosl.org,
linux-kernel@vger.kernel.org, przemyslaw.kitszel@intel.com
Subject: [PATCH net-next v2 4/9] virtchnl: Add header dependencies
Date: Wed, 27 Sep 2023 10:31:30 +0200 [thread overview]
Message-ID: <20230927083135.3237206-5-ivecera@redhat.com> (raw)
In-Reply-To: <20230927083135.3237206-1-ivecera@redhat.com>
The <linux/avf/virtchnl.h> uses BIT, struct_size and ETH_ALEN macros
but does not include appropriate header files that defines them.
Add these dependencies so this header file can be included anywhere.
Signed-off-by: Ivan Vecera <ivecera@redhat.com>
---
include/linux/avf/virtchnl.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/include/linux/avf/virtchnl.h b/include/linux/avf/virtchnl.h
index dd71d3009771..6b3acf15be5c 100644
--- a/include/linux/avf/virtchnl.h
+++ b/include/linux/avf/virtchnl.h
@@ -4,6 +4,10 @@
#ifndef _VIRTCHNL_H_
#define _VIRTCHNL_H_
+#include <linux/bitops.h>
+#include <linux/overflow.h>
+#include <uapi/linux/if_ether.h>
+
/* Description:
* This header file describes the Virtual Function (VF) - Physical Function
* (PF) communication protocol used by the drivers for all devices starting
--
2.41.0
next prev parent reply other threads:[~2023-09-27 8:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 8:31 [PATCH net-next v2 0/9] i40e: House-keeping and clean-up Ivan Vecera
2023-09-27 8:31 ` [PATCH net-next v2 1/9] i40e: Remove back pointer from i40e_hw structure Ivan Vecera
2023-10-05 8:08 ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
2023-09-27 8:31 ` [PATCH net-next v2 2/9] i40e: Move I40E_MASK macro to i40e_register.h Ivan Vecera
2023-10-05 8:10 ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
2023-09-27 8:31 ` [PATCH net-next v2 3/9] i40e: Refactor I40E_MDIO_CLAUSE* macros Ivan Vecera
2023-10-05 8:12 ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
2023-09-27 8:31 ` Ivan Vecera [this message]
2023-09-27 8:31 ` [PATCH net-next v2 5/9] i40e: Simplify memory allocation functions Ivan Vecera
2023-10-05 8:14 ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
2023-09-27 8:31 ` [PATCH net-next v2 6/9] i40e: Move memory allocation structures to i40e_alloc.h Ivan Vecera
2023-10-05 8:16 ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
2023-09-27 8:31 ` [PATCH net-next v2 7/9] i40e: Split i40e_osdep.h Ivan Vecera
2023-10-05 8:18 ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
2023-09-27 8:31 ` [PATCH net-next v2 8/9] i40e: Remove circular header dependencies and fix headers Ivan Vecera
2023-10-05 8:22 ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
2023-09-27 8:31 ` [PATCH net-next v2 9/9] i40e: Move DDP specific macros and structures to i40e_ddp.c Ivan Vecera
2023-10-05 8:23 ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
2023-09-27 8:53 ` [PATCH net-next v2 0/9] i40e: House-keeping and clean-up Przemek Kitszel
2023-09-28 22:12 ` Jesse Brandeburg
2023-10-04 19:17 ` Jakub Kicinski
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=20230927083135.3237206-5-ivecera@redhat.com \
--to=ivecera@redhat.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=poros@redhat.com \
--cc=przemyslaw.kitszel@intel.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;
as well as URLs for NNTP newsgroup(s).