Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Keller <jacob.e.keller@intel.com>
To: Diomidis Spinellis <dds@aueb.gr>,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	Przemek Kitszel <przemyslaw.kitszel@intel.com>
Cc: <intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] [PATCH] ixgbe: Break include dependency cycle
Date: Thu, 17 Oct 2024 13:36:25 -0700	[thread overview]
Message-ID: <88e7ae89-27d2-4e17-8f82-f71f68bd26aa@intel.com> (raw)
In-Reply-To: <20241017085851.1800065-1-dds@aueb.gr>



On 10/17/2024 1:58 AM, Diomidis Spinellis wrote:
> Header ixgbe_type.h includes ixgbe_mbx.h.  Also, header
> ixgbe_mbx.h included ixgbe_type.h, thus introducing a circular
> dependency.
> 
> - Remove ixgbe_mbx.h inclusion from ixgbe_type.h.
> 
> - ixgbe_mbx.h requires the definition of struct ixgbe_mbx_operations
>   so move its definition there. While at it, add missing argument
>   identifier names.
> 
> - Add required forward structure declarations.
> 
> - Include ixgbe_mbx.h in the .c files that need it, for the
>   following reasons:
> 
>   ixgbe_sriov.c uses ixgbe_check_for_msg
>   ixgbe_main.c uses ixgbe_init_mbx_params_pf
>   ixgbe_82599.c uses mbx_ops_generic
>   ixgbe_x540.c uses mbx_ops_generic
>   ixgbe_x550.c uses mbx_ops_generic
> 
> Signed-off-by: Diomidis Spinellis <dds@aueb.gr>
> ---

The changes make sense. Which tree was this aimed at? I'd guess as a
cleanup without direct impact that its aimed at next?

Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>

Thanks,
Jake

  reply	other threads:[~2024-10-17 20:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17  8:58 [Intel-wired-lan] [PATCH] ixgbe: Break include dependency cycle Diomidis Spinellis
2024-10-17 20:36 ` Jacob Keller [this message]
2024-10-17 20:52   ` Diomidis Spinellis
2024-10-28 10:05 ` Romanowski, Rafal

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=88e7ae89-27d2-4e17-8f82-f71f68bd26aa@intel.com \
    --to=jacob.e.keller@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=dds@aueb.gr \
    --cc=intel-wired-lan@lists.osuosl.org \
    --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