Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/display: Add header file for struct seq_file
Date: Mon, 26 Jun 2023 09:54:55 +0300	[thread overview]
Message-ID: <87mt0myaps.fsf@intel.com> (raw)
In-Reply-To: <20230626061043.1162688-1-chaitanya.kumar.borah@intel.com>

On Mon, 26 Jun 2023, Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com> wrote:
> With change [1], visibility of struct seq_file is lost in
> intel_display_power.h leading to build errors. Add header
> file explicitly to restore visibility.
>
> [1] ef104443bffa ("procfs: consolidate arch_report_meminfo declaration")
>
> Signed-off-by: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_display_power.h | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display_power.h b/drivers/gpu/drm/i915/display/intel_display_power.h
> index be1a87bde0c9..888993079a7b 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_power.h
> +++ b/drivers/gpu/drm/i915/display/intel_display_power.h
> @@ -6,6 +6,8 @@
>  #ifndef __INTEL_DISPLAY_POWER_H__
>  #define __INTEL_DISPLAY_POWER_H__
>  
> +#include <linux/seq_file.h>
> +

Always prefer a forward declaration over an include when it's
sufficient.

BR,
Jani.


>  #include "intel_wakeref.h"
>  
>  enum aux_ch;

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2023-06-26  6:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26  6:10 [Intel-gfx] [PATCH] drm/i915/display: Add header file for struct seq_file Chaitanya Kumar Borah
2023-06-26  6:54 ` Jani Nikula [this message]
2023-06-26  8:07   ` Borah, Chaitanya Kumar
2023-06-26  7:52 ` [Intel-gfx] [PATCH] drm/i915/display: Add forward declaration " Chaitanya Kumar Borah
2023-06-26 12:06   ` Jani Nikula
2023-06-26 13:44     ` Borah, Chaitanya Kumar
2023-06-26 14:35       ` Jani Nikula
2023-06-27  8:04         ` Borah, Chaitanya Kumar
2023-06-27  9:47           ` Jani Nikula
2023-06-27  9:50             ` Borah, Chaitanya Kumar
2023-06-26 10:31 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/display: Add header file for struct seq_file (rev2) Patchwork
2023-06-26 10:31 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-06-26 10:45 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-06-26 18:09 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork

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=87mt0myaps.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=chaitanya.kumar.borah@intel.com \
    --cc=intel-gfx@lists.freedesktop.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