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 forward declaration for struct seq_file
Date: Mon, 26 Jun 2023 15:06:55 +0300 [thread overview]
Message-ID: <87r0pyv34w.fsf@intel.com> (raw)
In-Reply-To: <20230626075254.1183894-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 forward
> declaration.
>
> [1] ef104443bffa ("procfs: consolidate arch_report_meminfo declaration")
>
> v2: Use forward declaration instead of headerfile inclusion [Jani]
>
> Signed-off-by: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
Hey, thanks for the patch, this would've been fine, but looks like Imre
just pushed commit f4fab137dd2b ("drm/i915: Add missing forward
declarations/includes to display power headers") which adds the forward
declaration among other things.
Sorry for the trouble.
BR,
Jani.
> ---
> drivers/gpu/drm/i915/display/intel_display_power.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display_power.h b/drivers/gpu/drm/i915/display/intel_display_power.h
> index be1a87bde0c9..0ba268e566b0 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_power.h
> +++ b/drivers/gpu/drm/i915/display/intel_display_power.h
> @@ -16,6 +16,7 @@ enum port;
> struct drm_i915_private;
> struct i915_power_well;
> struct intel_encoder;
> +struct seq_file;
>
> /*
> * Keep the pipe, transcoder, port (DDI_LANES,DDI_IO,AUX) domain instances
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-06-26 12:07 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
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 [this message]
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=87r0pyv34w.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