From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
intel-gfx@lists.freedesktop.org
Subject: Re: linux-next: Tree for Jun 13 (drivers/gpu/drm/i915/display/)
Date: Tue, 13 Jun 2023 08:39:44 -0700 [thread overview]
Message-ID: <89adc1ac-25a0-6eb6-4cc9-ab6cc8d49730@infradead.org> (raw)
In-Reply-To: <20230613165903.5cc10e58@canb.auug.org.au>
On 6/12/23 23:59, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20230609:
>
In file included from <command-line>:
./../drivers/gpu/drm/i915/display/intel_display_power.h:255:70: error: 'struct seq_file' declared inside parameter list will not be visible outside of this definition or declaration [-Werror]
255 | void intel_display_power_debug(struct drm_i915_private *i915, struct seq_file *m);
| ^~~~~~~~
cc1: all warnings being treated as errors
In file included from ./../drivers/gpu/drm/i915/display/intel_display_power_well.h:10,
from <command-line>:
./../drivers/gpu/drm/i915/display/intel_display_power.h:255:70: error: 'struct seq_file' declared inside parameter list will not be visible outside of this definition or declaration [-Werror]
255 | void intel_display_power_debug(struct drm_i915_private *i915, struct seq_file *m);
| ^~~~~~~~
cc1: all warnings being treated as errors
--
~Randy
next prev parent reply other threads:[~2023-06-13 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 6:59 linux-next: Tree for Jun 13 Stephen Rothwell
2023-06-13 14:51 ` linux-next: Tree for Jun 13 (drivers/block/swim3.c) Randy Dunlap
2023-06-13 15:39 ` Randy Dunlap [this message]
2023-06-13 16:21 ` linux-next: Tree for Jun 13 (drivers/net/ethernet/freescale/fs_enet/mii-fec.c) Randy Dunlap
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=89adc1ac-25a0-6eb6-4cc9-ab6cc8d49730@infradead.org \
--to=rdunlap@infradead.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®