Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Vecera <ivecera@redhat.com>
To: netdev@vger.kernel.org
Cc: edumazet@google.com, intel-wired-lan@lists.osuosl.org,
	jesse.brandeburg@intel.com, linux-kernel@vger.kernel.org,
	anthony.l.nguyen@intel.com, kuba@kernel.org, pabeni@redhat.com,
	davem@davemloft.net
Subject: [Intel-wired-lan] [PATCH net-next 4/9] virtchnl: Add header dependencies
Date: Tue, 26 Sep 2023 20:27:05 +0200	[thread overview]
Message-ID: <20230926182710.2517901-5-ivecera@redhat.com> (raw)
In-Reply-To: <20230926182710.2517901-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

_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

  parent reply	other threads:[~2023-09-26 18:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-26 18:27 [Intel-wired-lan] [PATCH net-next 0/9] i40e: House-keeping and clean-up Ivan Vecera
2023-09-26 18:27 ` [Intel-wired-lan] [PATCH net-next 1/9] i40e: Remove back pointer from i40e_hw structure Ivan Vecera
2023-09-26 18:27 ` [Intel-wired-lan] [PATCH net-next 2/9] i40e: Move I40E_MASK macro to i40e_register.h Ivan Vecera
2023-09-26 18:27 ` [Intel-wired-lan] [PATCH net-next 3/9] i40e: Refactor I40E_MDIO_CLAUSE* macros Ivan Vecera
2023-09-26 18:27 ` Ivan Vecera [this message]
2023-09-26 18:27 ` [Intel-wired-lan] [PATCH net-next 5/9] i40e: Remove circular header dependencies and fix headers Ivan Vecera
2023-09-26 18:27 ` [Intel-wired-lan] [PATCH net-next 6/9] i40e: Move DDP specific macros and structures to i40e_ddp.c Ivan Vecera
2023-09-26 18:27 ` [Intel-wired-lan] [PATCH net-next 7/9] i40e: Move memory allocation structures to i40e_alloc.h Ivan Vecera
2023-09-26 19:57   ` Przemek Kitszel
2023-09-27  7:08     ` Ivan Vecera
2023-09-26 18:27 ` [Intel-wired-lan] [PATCH net-next 8/9] i40e: Split i40e_osdep.h Ivan Vecera
2023-09-26 18:27 ` [Intel-wired-lan] [PATCH net-next 9/9] i40e: Simplify memory allocation functions Ivan Vecera

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=20230926182710.2517901-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=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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